From: Thomas Gleixner <tglx@linutronix.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Ingo Molnar" <mingo@kernel.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"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: Tue, 16 Jan 2018 16:08:20 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1801161606510.1823@nanos> (raw)
In-Reply-To: <1b2f251b-70ae-11fd-dab7-8d1180de483b@redhat.com>
On Tue, 16 Jan 2018, Paolo Bonzini wrote:
> On 16/01/2018 01:55, Ingo Molnar wrote:
> >
> > * Paolo Bonzini <pbonzini@redhat.com> wrote:
> >
> >> On 15/01/2018 19:36, Thomas Gleixner wrote:
> >>>> 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.
> >>
> >> I do understand why you want this to go through TIP, but I'm not sure
> >> why a change to Processor Tracing is related to PTI or retpolines. I'm
> >> also not sure why it is a problem for backportability, since we always
> >> try to send pull requests after TIP. Is it because 7*32+15 will be free
> >> in 4.16 but not earlier?
> >
> > It is because certain central x86 changes (such as changes to processor flags)
> > are kept on a v4.14 base to keep the PTI backporting efforts manageable.
> >
> > Please revert (or rebase) this change from the KVM tree, and submit it separately,
> > as it should have been done to begin with. Please also follow this process in the
> > future: all x86 changes outside arch/x86/kvm/ need an explicit ack from an x86
> > maintainer.
>
> I've always done it like that until
> https://marc.info/?l=kvm&m=149335647027790 got no response for three
> months, then I thought you didn't care.
Well, I certainly cared, but was kaisered enough to not look.
> We will drop Intel PT support and delay it to 4.17. Luwei, since your
> patches have issues with incorrect use of the MSR bitmap, this is
> probably a good thing anyway (better bisectability). Please repost your
> patches at the end of the merge window, then we will wait for an ack
> from Thomas/Ingo/Peter.
Can we get all cpu feature bit specific patches now please so we can move
them through TIP?
Thanks,
tglx
prev parent reply other threads:[~2018-01-16 15:08 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
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 [this message]
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.1801161606510.1823@nanos \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=dwmw@amazon.co.uk \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rkrcmar@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=thomas.lendacky@amd.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