From: "H.J. Lu" <hjl.tools@gmail.com>
To: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] x86: Don't check PTWRITE in tst-cpu-features-cpuinfo.c
Date: Sat, 12 Feb 2022 07:50:32 -0800 [thread overview]
Message-ID: <CAMe9rOr7Hgho0=8HRamgOGHBRGQ1GF0bB=MinzeLcMvenwBjXQ@mail.gmail.com> (raw)
In-Reply-To: <20220126202833.1810866-1-hjl.tools@gmail.com>
On Wed, Jan 26, 2022 at 12:28 PM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> Don't check PTWRITE against /proc/cpuinfo since kernel doesn't report
> PTWRITE in /proc/cpuinfo.
> ---
> sysdeps/x86/tst-cpu-features-cpuinfo.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/sysdeps/x86/tst-cpu-features-cpuinfo.c b/sysdeps/x86/tst-cpu-features-cpuinfo.c
> index 91a656b61d..981b2be5fd 100644
> --- a/sysdeps/x86/tst-cpu-features-cpuinfo.c
> +++ b/sysdeps/x86/tst-cpu-features-cpuinfo.c
> @@ -218,7 +218,10 @@ do_test (int argc, char **argv)
> fails += CHECK_PROC (popcnt, POPCNT);
> fails += CHECK_PROC (3dnowprefetch, PREFETCHW);
> fails += CHECK_PROC (prefetchwt1, PREFETCHWT1);
> +#if 0
> + /* NB: /proc/cpuinfo doesn't report this feature. */
> fails += CHECK_PROC (ptwrite, PTWRITE);
> +#endif
> fails += CHECK_PROC (pse, PSE);
> fails += CHECK_PROC (pse36, PSE_36);
> fails += CHECK_PROC (psn, PSN);
> --
> 2.34.1
>
I will check in this next Monday to fix the test on Intel Alder Lake.
--
H.J.
prev parent reply other threads:[~2022-02-12 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 20:28 H.J. Lu
2022-02-12 15:50 ` 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='CAMe9rOr7Hgho0=8HRamgOGHBRGQ1GF0bB=MinzeLcMvenwBjXQ@mail.gmail.com' \
--to=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).