From: Borislav Petkov <bp@alien8•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Sean Christopherson <seanjc@google•com>,
Thomas Gleixner <tglx@linutronix•de>,
Ingo Molnar <mingo@kernel•org>, "H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>,
Babu Moger <babu.moger@amd•com>,
Dave Hansen <dave.hansen@linux•intel.com>,
Elena Reshetova <elena.reshetova@intel•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
"Naveen N Rao (AMD)" <naveen@kernel•org>
Subject: Re: linux-next: manual merge of the kvm-x86 tree with the tip tree
Date: Tue, 25 Nov 2025 08:09:55 +0100 [thread overview]
Message-ID: <20251125070955.GAaSVWQ1i7l4EVzFV1@fat_crate.local> (raw)
In-Reply-To: <20251125155953.01b486f2@canb.auug.org.au>
On Tue, Nov 25, 2025 at 03:59:53PM +1100, Stephen Rothwell wrote:
> diff --cc arch/x86/include/asm/cpufeatures.h
> index d90ce601917c,646d2a77a2e2..000000000000
> --- a/arch/x86/include/asm/cpufeatures.h
> +++ b/arch/x86/include/asm/cpufeatures.h
> @@@ -503,9 -500,12 +504,15 @@@
> #define X86_FEATURE_IBPB_EXIT_TO_USER (21*32+14) /* Use IBPB on exit-to-userspace, see VMSCAPE bug */
> #define X86_FEATURE_ABMC (21*32+15) /* Assignable Bandwidth Monitoring Counters */
> #define X86_FEATURE_MSR_IMM (21*32+16) /* MSR immediate form instructions */
> -#define X86_FEATURE_X2AVIC_EXT (21*32+17) /* AMD SVM x2AVIC support for 4k vCPUs */
> -#define X86_FEATURE_CLEAR_CPU_BUF_VM_MMIO (21*32+18) /*
> +#define X86_FEATURE_SGX_EUPDATESVN (21*32+17) /* Support for ENCLS[EUPDATESVN] instruction */
> +
> +#define X86_FEATURE_SDCIAE (21*32+18) /* L3 Smart Data Cache Injection Allocation Enforcement */
> ++#define X86_FEATURE_X2AVIC_EXT (21*32+19) /* AMD SVM x2AVIC support for 4k vCPUs */
> ++#define X86_FEATURE_CLEAR_CPU_BUF_VM_MMIO (21*32+20) /*
> + * Clear CPU buffers before VM-Enter if the vCPU
> + * can access host MMIO (ignored for all intents
> + * and purposes if CLEAR_CPU_BUF_VM is set).
> + */
Yeah, I caught this already during review, we will make sure to let Linus know
when we send the pull requests.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2025-11-25 7:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 4:59 linux-next: manual merge of the kvm-x86 tree with the tip tree Stephen Rothwell
2025-11-25 7:09 ` Borislav Petkov [this message]
2025-12-04 5:10 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2026-05-27 14:22 Mark Brown
2026-05-18 16:10 Mark Brown
2026-03-04 12:21 Mark Brown
2026-03-04 23:10 ` Sean Christopherson
2026-03-05 19:24 ` Nathan Chancellor
2026-03-06 13:24 ` Mark Brown
2026-03-06 22:48 ` Nathan Chancellor
2025-11-20 4:52 Stephen Rothwell
2025-11-20 4:46 Stephen Rothwell
2025-10-20 0:07 Stephen Rothwell
2025-09-22 9:50 Mark Brown
2025-09-22 11:27 ` Aithal, Srikanth
2025-09-22 11:40 ` Mark Brown
2025-09-22 13:23 ` Mark Brown
2025-09-22 14:04 ` Sean Christopherson
2025-09-30 18:13 ` Paolo Bonzini
2025-09-19 13:50 Mark Brown
2025-01-06 4:05 Stephen Rothwell
2025-01-09 19:18 ` Sean Christopherson
2025-01-23 3:25 ` Stephen Rothwell
2024-02-07 4:35 Stephen Rothwell
2023-01-19 23:54 Stephen Rothwell
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=20251125070955.GAaSVWQ1i7l4EVzFV1@fat_crate.local \
--to=bp@alien8$(echo .)de \
--cc=babu.moger@amd$(echo .)com \
--cc=dave.hansen@linux$(echo .)intel.com \
--cc=elena.reshetova@intel$(echo .)com \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@kernel$(echo .)org \
--cc=naveen@kernel$(echo .)org \
--cc=peterz@infradead$(echo .)org \
--cc=seanjc@google$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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