From: "H.J. Lu" <hjl.tools@gmail.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] x86: Use CHECK_FEATURE_PRESENT to check HLE [BZ #27398]
Date: Tue, 1 Feb 2022 05:43:06 -0800 [thread overview]
Message-ID: <CAMe9rOpxQNmZL+=k3-QebCgZGaTU2VKfS-9sCw-_Xp_-oZ=SAQ@mail.gmail.com> (raw)
In-Reply-To: <60e40abc-136f-b09c-3c8d-dc35c01f967a@redhat.com>
On Wed, Jan 26, 2022 at 8:54 PM Carlos O'Donell <carlos@redhat.com> wrote:
>
> 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.
>
I am backporting this to release branches.
--
H.J.
prev parent reply other threads:[~2022-02-01 13:43 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
2022-02-01 13:43 ` H.J. Lu [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='CAMe9rOpxQNmZL+=k3-QebCgZGaTU2VKfS-9sCw-_Xp_-oZ=SAQ@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=carlos@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).