From: Thomas Gleixner <tglx@linutronix•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: "Paolo Bonzini" <pbonzini@redhat•com>,
"Radim Krčmář" <rkrcmar@redhat•com>, KVM <kvm@vger•kernel.org>,
"Ingo Molnar" <mingo@elte•hu>, "H. Peter Anvin" <hpa@zytor•com>,
"Peter Zijlstra" <peterz@infradead•org>,
"Linux-Next Mailing List" <linux-next@vger•kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger•kernel.org>,
"David Woodhouse" <dwmw@amazon•co.uk>,
"Tom Lendacky" <thomas.lendacky@amd•com>,
"Brijesh Singh" <brijesh.singh@amd•com>,
"Borislav Petkov" <bp@alien8•de>
Subject: Re: linux-next: manual merge of the kvm tree with Linus' and the tip trees
Date: Mon, 15 Jan 2018 19:36:54 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1801151933470.2143@nanos> (raw)
In-Reply-To: <alpine.DEB.2.20.1801151125040.1810@nanos>
On Mon, 15 Jan 2018, Thomas Gleixner wrote:
> On Mon, 15 Jan 2018, Stephen Rothwell wrote:
> > Hi all,
> > --- a/arch/x86/include/asm/cpufeatures.h
> > +++ b/arch/x86/include/asm/cpufeatures.h
> > @@@ -202,11 -201,9 +202,11 @@@
> > #define X86_FEATURE_HW_PSTATE ( 7*32+ 8) /* AMD HW-PState */
> > #define X86_FEATURE_PROC_FEEDBACK ( 7*32+ 9) /* AMD ProcFeedbackInterface */
> > #define X86_FEATURE_SME ( 7*32+10) /* AMD Secure Memory Encryption */
> > -#define X86_FEATURE_SEV ( 7*32+11) /* AMD Secure Encrypted Virtualization */
> > -
> > +#define X86_FEATURE_PTI ( 7*32+11) /* Kernel Page Table Isolation enabled */
> > +#define X86_FEATURE_RETPOLINE ( 7*32+12) /* Generic Retpoline mitigation for Spectre variant 2 */
> > +#define X86_FEATURE_RETPOLINE_AMD ( 7*32+13) /* AMD Retpoline mitigation for Spectre variant 2 */
> > #define X86_FEATURE_INTEL_PPIN ( 7*32+14) /* Intel Processor Inventory Number */
> > - #define X86_FEATURE_INTEL_PT ( 7*32+15) /* Intel Processor Trace */
>
> Where is that patch which moves INTEL_PT ?
>
> commit 632218d8dee296c8b397c13b7b3b4be090a1c043
> Author: Paolo Bonzini <pbonzini@redhat•com>
> Date: Mon Dec 11 04:30:50 2017 +0800
>
> x86: cpufeature: move processor tracing out of scattered features
>
> Processor tracing is already enumerated in word 9 (CPUID[7,0].EBX),
> so do not duplicate it in the scattered features word.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat•com>
>
> Can KVM folks please stop doing random changes to the cpufeatures code
> without talking to x86 maintainers and Borislav?
>
> This wants to go through TIP or at least reviewed and acked.
In fact it needs to go through TIP. We spent a lot of effort to make the
backporting of all this mess simple and this is just shooting a hole in it.
Please drop that change and we sort something out how it can be done proper.
Dammit, we have a well established process for stuff like that.
Thanks,
tglx
next prev parent reply other threads:[~2018-01-15 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 2:34 linux-next: manual merge of the kvm tree with Linus' and the tip trees Stephen Rothwell
2018-01-15 10:28 ` Thomas Gleixner
2018-01-15 18:36 ` Thomas Gleixner [this message]
2018-01-15 22:45 ` Paolo Bonzini
2018-01-16 0:55 ` Ingo Molnar
2018-01-16 13:37 ` Paolo Bonzini
2018-01-16 15:08 ` Thomas Gleixner
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=alpine.DEB.2.20.1801151933470.2143@nanos \
--to=tglx@linutronix$(echo .)de \
--cc=bp@alien8$(echo .)de \
--cc=brijesh.singh@amd$(echo .)com \
--cc=dwmw@amazon$(echo .)co.uk \
--cc=hpa@zytor$(echo .)com \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=pbonzini@redhat$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=rkrcmar@redhat$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=thomas.lendacky@amd$(echo .)com \
/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