Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: daichengrong <daichengrong@iscas.ac.cn>
To: "FFmpeg development discussions and patches"
	<ffmpeg-devel@ffmpeg.org>,
	"Rémi Denis-Courmont" <remi@remlab.net>
Subject: Re: [FFmpeg-devel] [PATCH] RISC-V:update ff_get_cpu_flags_riscv for RVV
Date: Thu, 20 Mar 2025 17:27:39 +0800
Message-ID: <266f9b7f-5065-44ba-8037-5c44e197b85e@iscas.ac.cn> (raw)
In-Reply-To: <413CE245-1F59-4222-B0C6-599C65390B13@remlab.net>

hi,

The reply email was mistakenly classified as spam, resulting in not 
being seen in time.

Late reply.

在 2025/3/15 12:03:09, Rémi Denis-Courmont :
> Hi,
>
> Le 14 mars 2025 17:32:57 GMT+07:00, daichengrong@iscas.ac.cn a écrit :
>> From: daichengrong <daichengrong@iscas.ac.cn>
>>
>> Availability of RVV and ZVBB should be determined with dl_hwcap.
> No. That's completely superfluous since we already check for kernel support with hwprobe().
No. If the operating system does not enable dl_hwcap support for rvv, an 
illegal instruction exception will be reported , even if the hardware 
and kernel support RVV.
> And we can't check for Zb* and Zv* with hwcap anyhow.
>
>> As those extensions rely on vector registers, kernel vector support
>> is required to save the state of context switching.
> No. Kernel context switching is already ascertained.
No. The kernel will not save and restore vector registers if the program 
does not use vector instructions.
> And we don't care about libc context support, since vectors are clobbered by function calls, e.g. for long jumps or ucontext.
I'm confused about this
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2025-03-20  9:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-14 10:32 daichengrong
2025-03-15  4:03 ` Rémi Denis-Courmont
2025-03-20  9:27   ` daichengrong [this message]
2025-03-20 11:17     ` Rémi Denis-Courmont
2025-03-21  2:12       ` daichengrong
2025-03-21  4:11         ` Rémi Denis-Courmont

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=266f9b7f-5065-44ba-8037-5c44e197b85e@iscas.ac.cn \
    --to=daichengrong@iscas.ac.cn \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=remi@remlab.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git