From: Like Xu <like.xu.linux@gmail.com>
To: Borislav Petkov <bp@alien8.de>
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 16:08:17 +0800 [thread overview]
Message-ID: <1105cf7d-0d61-3ae2-f372-3b1f80c08c60@gmail.com> (raw)
In-Reply-To: <YfVM+xdDS76E3d6r@zn.tnic>
On 29/1/2022 10:19 pm, Borislav Petkov wrote:
> On Wed, Jan 19, 2022 at 11:41:31AM +0800, Like Xu wrote:
>> Thanks Dave and Paolo. Just for your convenience:
>>
>> From 588c2221999c1f5860188a7cbaeb0d4f80c6d727 Mon Sep 17 00:00:00 2001
>> From: Like Xu <likexu@tencent.com>
>> Date: Mon, 17 Jan 2022 14:23:44 +0800
>> Subject: [PATCH v2] x86/cpufeatures: Move AMX CPU feature defines to correct
>> word location
>>
>> From: Like Xu <likexu@tencent.com>
>>
>> The word 18 for Intel-defined CPU features from CPUID level 0x00000007:0 (EDX)
>> has been defined in the same file. Move the definitions of X86_FEATURE_AMX_* to
>> the right entry to prevent misinterpretation. No functional change intended.
>>
>> Signed-off-by: Like Xu <likexu@tencent.com>
>> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>> v1 -> v2 Changelog:
>> - Refine the commit message and subject; (Dave)
>>
>> arch/x86/include/asm/cpufeatures.h | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> $ test-apply.sh /tmp/urgent.01
Emm, are you willing to make "test-apply.sh" public (or have done) and let
others benefit ?
> checking file arch/x86/include/asm/cpufeatures.h
> Hunk #1 FAILED at 299.
> patch: **** malformed patch at line 45: IBPB) */
>
> Don't ever send patches from
Got you.
>
> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
>
> That thing mangles them.
>
> See Documentation/process/email-clients.rst for further info.
>
Sorry for the late reply, and here's a new version from git-send-email:
https://lore.kernel.org/lkml/20220208080103.8119-1-likexu@tencent.com/
next prev parent reply other threads:[~2022-02-08 8:08 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 [this message]
2022-02-08 8:51 ` Borislav Petkov
2022-02-08 9:06 ` Like Xu
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=1105cf7d-0d61-3ae2-f372-3b1f80c08c60@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=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®