From: Borislav Petkov <bp@alien8.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Wanpeng Li" <kernellwp@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, kvm <kvm@vger.kernel.org>,
"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [PATCH] KVM: X86: Allow userspace to define the microcode version
Date: Mon, 26 Feb 2018 13:20:58 +0100 [thread overview]
Message-ID: <20180226122058.GF4377@pd.tnic> (raw)
In-Reply-To: <eeae3e95-c908-695a-043f-a99f8ed39919@redhat.com>
On Mon, Feb 26, 2018 at 12:47:27PM +0100, Paolo Bonzini wrote:
> It's actually 0x100000000.
Even more wrong. Revision ID is bits [31:0].
> Actually I think this patch makes sense, since some errata actually can
> be worked around in the guest in the same way as the host. However, it
> should also be tied to the recently introduced mechanism to read MSR
> contents from the host.
So if we decide to do microcode revisions in the guest, we should
consider the fact that microcode revisions need to be handled the same
way as CPUID bits: a revision number means something on baremetal and
implies a certain functionality, just like a set CPUID bit does.
So we either have that same functionality in the guest or we don't talk
about revisions at all. Because if we end up lying by coming up with
revision numbers, all hell will break loose in the guest.
IMO, of course.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-02-26 12:20 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 7:23 [PATCH] KVM: X86: Allow userspace to define the microcode version Wanpeng Li
2018-02-26 9:41 ` Borislav Petkov
2018-02-26 10:06 ` Wanpeng Li
2018-02-26 10:49 ` Borislav Petkov
2018-02-26 11:02 ` Wanpeng Li
2018-02-26 11:16 ` Borislav Petkov
2018-02-26 11:25 ` Wanpeng Li
2018-02-26 11:30 ` Borislav Petkov
2018-02-26 11:37 ` Wanpeng Li
2018-02-26 11:44 ` Borislav Petkov
2018-02-26 11:52 ` Wanpeng Li
2018-02-26 11:54 ` Paolo Bonzini
2018-02-26 12:15 ` Borislav Petkov
2018-02-26 12:16 ` Paolo Bonzini
2018-02-26 12:18 ` Paolo Bonzini
2018-02-26 12:22 ` Borislav Petkov
2018-02-26 12:41 ` Paolo Bonzini
2018-02-26 13:05 ` Borislav Petkov
2018-02-26 14:39 ` Konrad Rzeszutek Wilk
2018-02-26 14:46 ` Paolo Bonzini
2018-02-26 19:37 ` Borislav Petkov
2018-02-26 20:51 ` Konrad Rzeszutek Wilk
2018-02-26 21:30 ` Konrad Rzeszutek Wilk
2018-02-27 8:33 ` Paolo Bonzini
2018-03-08 9:24 ` [tip:x86/pti] x86/spectre_v2: Don't check microcode versions when running under hypervisors tip-bot for Konrad Rzeszutek Wilk
2018-04-17 10:40 ` [PATCH] KVM: X86: Allow userspace to define the microcode version Wanpeng Li
2018-04-17 20:24 ` Eduardo Habkost
2018-04-18 3:24 ` Wanpeng Li
2018-04-18 9:03 ` Eduardo Habkost
2018-04-18 10:36 ` Paolo Bonzini
2018-04-23 12:58 ` Borislav Petkov
2018-04-23 13:08 ` Eduardo Habkost
2018-04-23 13:23 ` Borislav Petkov
2018-04-23 16:03 ` Paolo Bonzini
2018-04-24 2:59 ` Wanpeng Li
2018-04-24 3:14 ` Konrad Rzeszutek Wilk
2018-04-24 5:09 ` Paolo Bonzini
2018-04-24 13:44 ` Konrad Rzeszutek Wilk
2018-04-24 2:56 ` Wanpeng Li
2018-02-26 11:47 ` Paolo Bonzini
2018-02-26 12:20 ` Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-26 9:26 Liran Alon
2018-02-26 10:08 ` Wanpeng Li
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=20180226122058.GF4377@pd.tnic \
--to=bp@alien8.de \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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