From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Mihai Carabas <mihai.carabas@oracle.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
David Woodhouse <dwmw@amazon.co.uk>,
KarimAllah Ahmed <karahmed@amazon.de>
Subject: Re: [PATCH v3 0/3] Per-VCPU MSR bitmaps patches - topic branch for x86/pti
Date: Thu, 1 Feb 2018 16:58:34 +0100 [thread overview]
Message-ID: <20180201155833.GE31080@flask> (raw)
In-Reply-To: <20180201014810.GA19582@char.us.oracle.com>
2018-01-31 20:48-0500, Konrad Rzeszutek Wilk:
> On Wed, Jan 31, 2018 at 04:09:21PM -0500, Paolo Bonzini wrote:
> > David and others,
> >
> > the following changes since commit ba804bb4b72e57374b5f567b783aa0298fba0ce6:
> >
> > Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2018-01-26 09:03:16 -0800)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/virt/kvm/kvm.git msr-bitmaps
> >
> > for you to fetch changes up to 904e14fb7cb96401a7dc803ca2863fd5ba32ffe6:
> >
> > KVM: VMX: make MSR bitmaps per-VCPU (2018-01-26 22:59:32 +0100)
> >
> > The patches are on top of Linus's tree and I checked that they apply okay
> > on top of the latest 4.14 tree as well as required for tip x86/pti.
> > One extra commit is needed that is pretty safe and would have been merged
> > for 4.16 anyway.
> >
> > Radim, please pull this into kvm.git too. As before I've placed my
> > resolution on kvm.git, branch refs/heads/msr-bitmaps-merge-resolution.
> > It's based on kvm/next this time.
>
> You don't want folks to review patch #2 and #3 first? There are tons
> of people that I am sure would be thrilled with the whole Spectra circus.
This is only a boring prerequisite that doesn't add any security ...
Jim Mattson gave r-b to [v1 3/3] and was a significant contributor to
the patches, David Hildenbrandt reviewed [v2 2,3/3] and there have been
only minor changes since.
v3 looks good to me, so I'll pull if there are no more requirements from
pti.
prev parent reply other threads:[~2018-02-01 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 21:09 [PATCH v3 0/3] Per-VCPU MSR bitmaps patches - topic branch for x86/pti Paolo Bonzini
2018-01-31 21:09 ` [PATCH 1/3] KVM: nVMX: Eliminate vmcs02 pool Paolo Bonzini
2018-01-31 21:09 ` [PATCH 2/3] KVM: VMX: introduce alloc_loaded_vmcs Paolo Bonzini
2018-01-31 21:09 ` [PATCH 3/3] KVM: VMX: make MSR bitmaps per-VCPU Paolo Bonzini
2018-02-01 1:48 ` [PATCH v3 0/3] Per-VCPU MSR bitmaps patches - topic branch for x86/pti Konrad Rzeszutek Wilk
2018-02-01 15:58 ` Radim Krčmář [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=20180201155833.GE31080@flask \
--to=rkrcmar@redhat.com \
--cc=dwmw@amazon.co.uk \
--cc=karahmed@amazon.de \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mihai.carabas@oracle.com \
--cc=pbonzini@redhat.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