From: "H.J. Lu" <hjl.tools@gmail.com>
To: Arjan van de Ven <arjan@linux.intel.com>,
Hongyu Wang <hongyu.wang@intel.com>,
liuhongt <hongtao.liu@intel.com>
Cc: Noah Goldstein <goldstein.w.n@gmail.com>,
Thiago Macieira <thiago.macieira@intel.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] x86: Don't set Prefer_No_AVX512 for processors with AVX512 and AVX-VNNI
Date: Tue, 7 Dec 2021 05:34:47 -0800 [thread overview]
Message-ID: <CAMe9rOqnJ9xgKbUiP10hPS33hpQF5g-cqHm3a6cgtwyk8RYoFw@mail.gmail.com> (raw)
In-Reply-To: <3639bca9-e90d-d3ff-c758-d2d5c4c0a3d2@linux.intel.com>
On Tue, Dec 7, 2021 at 5:18 AM Arjan van de Ven <arjan@linux.intel.com> wrote:
>
> On 12/7/2021 4:53 AM, H.J. Lu wrote:
> >> Should we also do Rocket Lake?
> >> According to Travis Downs at least downclocking is an issue there ether:
> >> https://travisdowns.github.io/blog/2020/08/19/icl-avx512-freq.html#rocket-lake
> >
> > Thiago, Arjan,
> >
> > Is this true that Rocket Lake can use ZMM load/store?
> >
>
>
> I have no specific data myself about rocket lake... but data is data...
> so I'm all for trying it, but other than looking at cpuid's model number
Hongtao, Hongyu, can you find a Rocket Lake to test?
> I wouldn't know of an easy way to detect RKL vs ICL or others
In GCC, RKL ISAs are ICL ISAs without SGX.
--
H.J.
next prev parent reply other threads:[~2021-12-07 13:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 3:23 H.J. Lu
2021-12-07 7:47 ` Noah Goldstein
2021-12-07 12:53 ` H.J. Lu
2021-12-07 13:17 ` Arjan van de Ven
2021-12-07 13:34 ` H.J. Lu [this message]
2021-12-07 14:05 ` Florian Weimer
2021-12-07 14:15 ` H.J. Lu
2021-12-07 15:47 ` Florian Weimer
2021-12-07 15:52 ` H.J. Lu
2021-12-07 16:22 ` Thiago Macieira
2021-12-07 19:32 ` Noah Goldstein
2022-04-23 1:51 ` Sunil Pandey
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=CAMe9rOqnJ9xgKbUiP10hPS33hpQF5g-cqHm3a6cgtwyk8RYoFw@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=arjan@linux.intel.com \
--cc=goldstein.w.n@gmail.com \
--cc=hongtao.liu@intel.com \
--cc=hongyu.wang@intel.com \
--cc=libc-alpha@sourceware.org \
--cc=thiago.macieira@intel.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).