From: Carlos O'Donell <carlos@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] x86: Use CHECK_FEATURE_PRESENT to check HLE [BZ #27398]
Date: Wed, 26 Jan 2022 23:54:16 -0500 [thread overview]
Message-ID: <60e40abc-136f-b09c-3c8d-dc35c01f967a@redhat.com> (raw)
In-Reply-To: <20220126205119.2000487-1-hjl.tools@gmail.com>
On 1/26/22 15:51, H.J. Lu wrote:
> HLE is disabled on blacklisted CPUs. Use CHECK_FEATURE_PRESENT, instead
> of CHECK_FEATURE_ACTIVE, to check HLE.
OK for glibc 2.35. Fixes the issue on my T590 with the resume issues.
Reviewed-by: Carlos O'Donell <carlos@redhat.com>
Tested-by: Carlos O'Donell <carlos@redhat.com>
> ---
> sysdeps/x86/tst-cpu-features-supports.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sysdeps/x86/tst-cpu-features-supports.c b/sysdeps/x86/tst-cpu-features-supports.c
> index 46b2c7bf83..9f10f02954 100644
> --- a/sysdeps/x86/tst-cpu-features-supports.c
> +++ b/sysdeps/x86/tst-cpu-features-supports.c
> @@ -130,7 +130,7 @@ do_test (int argc, char **argv)
> fails += CHECK_FEATURE_ACTIVE (gfni, GFNI);
> #endif
> #if __GNUC_PREREQ (11, 0)
> - fails += CHECK_FEATURE_ACTIVE (hle, HLE);
> + fails += CHECK_FEATURE_PRESENT (hle, HLE);
> fails += CHECK_FEATURE_PRESENT (ibt, IBT);
> fails += CHECK_FEATURE_ACTIVE (lahf_lm, LAHF64_SAHF64);
> fails += CHECK_FEATURE_PRESENT (lm, LM);
--
Cheers,
Carlos.
next prev parent reply other threads:[~2022-01-27 4:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 20:51 H.J. Lu
2022-01-27 4:54 ` Carlos O'Donell [this message]
2022-02-01 13:43 ` H.J. Lu
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=60e40abc-136f-b09c-3c8d-dc35c01f967a@redhat.com \
--to=carlos@redhat.com \
--cc=hjl.tools@gmail.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).