From: Florian Weimer <fweimer@redhat.com>
To: Stefan Liebler via Libc-alpha <libc-alpha@sourceware.org>
Cc: Stefan Liebler <stli@linux.ibm.com>
Subject: Re: [PATCH] S390: Influence hwcaps/stfle via GLIBC_TUNABLES.
Date: Mon, 06 Feb 2023 15:21:58 +0100 [thread overview]
Message-ID: <87lelavpq1.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20230202135750.1632859-1-stli@linux.ibm.com> (Stefan Liebler via Libc-alpha's message of "Thu, 2 Feb 2023 14:57:50 +0100")
* Stefan Liebler via Libc-alpha:
> This patch enables the option to influence hwcaps and stfle bits used
> by the s390 specific ifunc-resolvers. The currently x86-specific
> tunable glibc.cpu.hwcaps is also used on s390x to achieve the task. In
> addition the user can also set a CPU arch-level like z13 instead of
> single HWCAP and STFLE features.
>
> Note that the tunable only handles the features which are really used
> in the IFUNC-resolvers. All others are ignored as the values are only
> used inside glibc. Thus we can influence:
> - HWCAP_S390_VXRS (z13)
> - HWCAP_S390_VXRS_EXT (z14)
> - HWCAP_S390_VXRS_EXT2 (z15)
> - STFLE_MIE3 (z15)
>
> The influenced hwcap/stfle-bits are stored in the s390-specific
> cpu_features struct which also contains reserved fields for future
> usage.
>
> The ifunc-resolvers and users of stfle bits are adjusted to use the
> information from cpu_features struct.
>
> On 31bit, the ELF_MACHINE_IRELATIVE macro is now also defined.
> Otherwise the new ifunc-resolvers segfaults as they depend on
> the not yet processed_rtld_global_ro@GLIBC_PRIVATE relocation.
> ---
I think you are updating all the right places. You should probably push
this as the hardware maintainer.
Thanks,
Florian
next prev parent reply other threads:[~2023-02-06 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 13:57 Stefan Liebler
2023-02-06 14:21 ` Florian Weimer [this message]
2023-02-07 8:22 ` Stefan Liebler
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=87lelavpq1.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=stli@linux.ibm.com \
/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).