From: Like Xu <like.xu.linux@gmail.com>
To: Borislav Petkov <bp@alien8.de>, Jim Mattson <jmattson@google.com>
Cc: Dave Hansen <dave.hansen@intel.com>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Jing Liu <jing2.liu@intel.com>,
linux-kernel@vger.kernel.org, "Bae,
Chang Seok" <chang.seok.bae@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86/cpufeatures: Move the definition of X86_FEATURE_AMX_* to the word 18
Date: Tue, 8 Feb 2022 17:06:04 +0800 [thread overview]
Message-ID: <f3a9ccd2-bd6c-691a-f6c2-43fb549b3d4b@gmail.com> (raw)
In-Reply-To: <YgIvCIEeWK0wnq8M@zn.tnic>
On 8/2/2022 4:51 pm, Borislav Petkov wrote:
> On Tue, Feb 08, 2022 at 04:08:17PM +0800, Like Xu wrote:
>> Emm, are you willing to make "test-apply.sh" public (or have done) and let
>> others benefit ?
>
> It is nothing special - just a simple script which does first
>
> patch -p1 --dry-run -l -i [patch file]
>
> to see whether it would even apply.
>
>> Sorry for the late reply, and here's a new version from git-send-email:
>
> Yeah, someone already took care of this:
>
> https://git.kernel.org/tip/ae75fa54228162ecd65341f9780886f21f557cc4
>
Uh, it's Jim and we have worked together on many KVM issues.
BTW, I'm not sure why we prefer:
#define X86_FEATURE_AVX512_FP16 (18*32+23) /* AVX512 FP16 */
#define X86_FEATURE_SPEC_CTRL (18*32+26) /* "" Speculation Control (IBRS + IBPB) */
+#define X86_FEATURE_AMX_BF16 (18*32+22) /* AMX bf16 Support */
+#define X86_FEATURE_AMX_TILE (18*32+24) /* AMX tile Support */
+#define X86_FEATURE_AMX_INT8 (18*32+25) /* AMX int8 Support */
rather than:
+#define X86_FEATURE_AMX_BF16 (18*32+22) /* AMX bf16 Support */
#define X86_FEATURE_AVX512_FP16 (18*32+23) /* AVX512 FP16 */
+#define X86_FEATURE_AMX_TILE (18*32+24) /* AMX tile Support */
+#define X86_FEATURE_AMX_INT8 (18*32+25) /* AMX int8 Support */
It would make more sense to put them in order, what do you think? Need v3 to
sort it ?
Thanks,
Like Xu
next prev parent reply other threads:[~2022-02-08 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 6:23 Like Xu
2022-01-17 8:24 ` Paolo Bonzini
2022-01-18 17:11 ` Dave Hansen
2022-01-18 17:15 ` Paolo Bonzini
2022-01-19 3:41 ` Like Xu
2022-01-29 14:19 ` Borislav Petkov
2022-02-08 8:08 ` Like Xu
2022-02-08 8:51 ` Borislav Petkov
2022-02-08 9:06 ` Like Xu [this message]
2022-02-08 9:21 ` Borislav Petkov
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=f3a9ccd2-bd6c-691a-f6c2-43fb549b3d4b@gmail.com \
--to=like.xu.linux@gmail.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=jing2.liu@intel.com \
--cc=jmattson@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®