Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Brad Smith <brad-at-comstyle.com@ffmpeg.org>
To: "FFmpeg development discussions and patches"
	<ffmpeg-devel@ffmpeg.org>,
	"Rémi Denis-Courmont" <remi@remlab.net>
Subject: Re: [FFmpeg-devel] [PATCH] lavu/riscv: do not fallback to AT_HWCAP auxillary vector
Date: Fri, 19 Jul 2024 17:28:23 -0400
Message-ID: <f9ad2b34-3038-4523-8347-ff6418f92d84@comstyle.com> (raw)
In-Reply-To: <20240719154623.3546-1-remi@remlab.net>

On 2024-07-19 11:46 a.m., Rémi Denis-Courmont wrote:
> If __riscv_hwprobe() fails, then the kernel version is presumably too
> old. There is not much point falling back to the auxillary vector.
>
> - The Linux kernel requires I, so the flag is always set on Linux, and
>    run-time detection is unnecessary. Our RISC-V assembler does anyway not
>    support targets without I.
>
> - Linux can compile with or without F and D, but it cannot perform
>    run-time detection for them (a kernel with F support will not boot a
>    processor without F). The run-time detection is thus useless in that
>    case. Besides F and D extensions are used throughout the C code, so
>    their run-time detection would not be practical.
>
> - Support for V was added in a later kernel version than riscv_hwprobe(),
>    so the system call will always be available if the kernel supports V.
>    The only exception would be vendor kernel forks, but those are known to
>    haphasardly pretend to support V on systems without actual V support, or
>    with only pre-ratification binary-incompatible version. Furthermore, a
>    large chunk of our optimisations require Zba and/or Zbb which cannot be
>    detected with HWCAP in those kernels.
>
> For what it is worth, OpenJDK already took a similar action. Note that this
> keeps AT_HWCAP usage for platforms with neither C run-time <sys/hwprobe.h>
> nor kernel <asm/hwprobe.h>, notably kernels other than Linux.

Thanks for the last part. The bits for OpenBSD have just landed for 
supporting
elf_aux_info() so I'll look at adding support for FreeBSD and OpenBSD.

> ---
>   libavutil/riscv/cpu.c | 5 ++---
>   1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/libavutil/riscv/cpu.c b/libavutil/riscv/cpu.c
> index 73abd289a6..04ac404bbf 100644
> --- a/libavutil/riscv/cpu.c
> +++ b/libavutil/riscv/cpu.c
> @@ -83,9 +83,8 @@ int ff_get_cpu_flags_riscv(void)
>                   break;
>               default:
>           }
> -    } else
> -#endif
> -#if HAVE_GETAUXVAL
> +    }
> +#elif HAVE_GETAUXVAL
>       {
>           const unsigned long hwcap = getauxval(AT_HWCAP);
>   
_______________________________________________
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:[~2024-07-19 21:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-19 15:46 Rémi Denis-Courmont
2024-07-19 21:28 ` Brad Smith [this message]
2024-07-21 11:22   ` 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=f9ad2b34-3038-4523-8347-ff6418f92d84@comstyle.com \
    --to=brad-at-comstyle.com@ffmpeg.org \
    --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