linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"Liran Alon" <liran.alon@oracle.com>,
	"Nadav Amit" <nadav.amit@gmail.com>
Subject: Re: [PATCH v4] KVM: X86: Allow userspace to define the microcode version
Date: Tue, 27 Feb 2018 10:43:03 +0100	[thread overview]
Message-ID: <20180227094303.GA30022@pd.tnic> (raw)
In-Reply-To: <b6051971-04a5-09e7-d11f-3689369292fe@redhat.com>

On Tue, Feb 27, 2018 at 09:38:12AM +0100, Paolo Bonzini wrote:
> On 27/02/2018 03:35, Wanpeng Li wrote:
> > From: Wanpeng Li <wanpengli@tencent.com>
> > 
> > Linux (among the others) has checks to make sure that certain features 
> > aren't enabled on a certain family/model/stepping if the microcode version 
> > isn't greater than or equal to a known good version.
> > 
> > By exposing the real microcode version, we're preventing buggy guests that
> > don't check that they are running virtualized (i.e., they should trust the
> > hypervisor) from disabling features that are effectively not buggy.
> > 
> > Suggested-by: Filippo Sironi <sironi@amazon.de>
> > Cc: Paolo Bonzini <pbonzini@redhat.com>
> > Cc: Radim Krčmář <rkrcmar@redhat.com>
> > Cc: Liran Alon <liran.alon@oracle.com>
> > Cc: Nadav Amit <nadav.amit@gmail.com>
> > Signed-off-by: Wanpeng Li <wanpengli@tencent.com>
> > ---
> > v3 -> v4:
> >  * add the shifts back
> 
> Please wait for a review instead of pushing new versions continuously.

... and pls CC me on your submissions.

Thx.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

  parent reply	other threads:[~2018-02-27  9:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27  2:35 [PATCH v4] KVM: X86: Allow userspace to define the microcode version Wanpeng Li
2018-02-27  8:38 ` Paolo Bonzini
2018-02-27  9:26   ` Wanpeng Li
2018-02-27 10:22     ` Paolo Bonzini
2018-02-27  9:43   ` Borislav Petkov [this message]
2018-02-27 14:17 ` Tom Lendacky

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=20180227094303.GA30022@pd.tnic \
    --to=bp@alien8.de \
    --cc=kernellwp@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liran.alon@oracle.com \
    --cc=nadav.amit@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@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;
as well as URLs for NNTP newsgroup(s).