From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: 'GNU C Library' <libc-alpha@sourceware.org>
Subject: Re: [PATCH] AArch64: Check kernel version for SVE ifuncs
Date: Mon, 18 Mar 2024 14:22:39 +0000 [thread overview]
Message-ID: <PAWPR08MB898299D96F77478EC7CB7956832D2@PAWPR08MB8982.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <8734snu5i3.fsf@oldenburg3.str.redhat.com>
Hi Florian,
> I would suggest to check for version >= 6.2 || version == 5.14.0. At
> this point, people running 5.14 are very likely on the el9 kernel or a
> derivative, and we have backported the upstream fix into it:
Thanks for checking that, I've updated the patch to exclude 5.14.0.
> I understand that this makes the check even uglier, but that's the
> nature of version checks. 8-(
Yes, but it's unavoidable if the kernel doesn't add performance related
HWCAPs for us to check. I cleaned up the parser a little by using the same
8:8:8 format as used by __LINUX_KERNEL_VERSION.
Cheers,
Wilco
prev parent reply other threads:[~2024-03-18 14:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 14:31 Wilco Dijkstra
2024-03-13 18:12 ` Adhemerval Zanella Netto
2024-03-13 19:25 ` Szabolcs Nagy
2024-03-13 19:55 ` Adhemerval Zanella Netto
2024-03-14 8:35 ` Szabolcs Nagy
2024-03-14 13:47 ` Adhemerval Zanella Netto
2024-03-14 14:26 ` Szabolcs Nagy
2024-03-14 14:28 ` Adhemerval Zanella Netto
2024-03-14 9:02 ` Florian Weimer
2024-03-13 18:39 ` Szabolcs Nagy
2024-03-13 19:31 ` Andrew Pinski
2024-03-13 20:44 ` Wilco Dijkstra
2024-03-14 9:06 ` Florian Weimer
2024-03-14 14:42 ` Wilco Dijkstra
2024-03-14 14:55 ` Florian Weimer
2024-03-14 15:38 ` Wilco Dijkstra
2024-03-14 16:52 ` Florian Weimer
2024-03-18 11:46 ` Florian Weimer
2024-03-18 14:22 ` Wilco Dijkstra [this message]
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=PAWPR08MB898299D96F77478EC7CB7956832D2@PAWPR08MB8982.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).