From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: [PATCH 0/2] KVM: x86: fixes for AMD speculation bug CPUID leaf
Date: Thu, 15 Aug 2019 09:41:21 +0200 [thread overview]
Message-ID: <1565854883-27019-1-git-send-email-pbonzini@redhat.com> (raw)
Patch 1 fixes the reporting of bugs and mitigations via the
0x8000_0008 CPUID leaf on Intel processors.
Patch 2 fixes the reporting of VIRT_SPEC availability on
AMD processors.
Paolo
Paolo Bonzini (2):
KVM: x86: fix reporting of AMD speculation bug CPUID leaf
KVM: x86: always expose VIRT_SSBD to guests
arch/x86/kvm/cpuid.c | 27 +++++++++++++++++----------
1 file changed, 17 insertions(+), 10 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-08-15 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 7:41 Paolo Bonzini [this message]
2019-08-15 7:41 ` [PATCH 1/2] KVM: x86: fix reporting of AMD speculation bug CPUID leaf Paolo Bonzini
2019-08-16 21:45 ` Jim Mattson
2019-08-19 15:18 ` Paolo Bonzini
2019-08-19 18:30 ` Jim Mattson
2019-08-19 18:33 ` Paolo Bonzini
2019-08-15 7:41 ` [PATCH 2/2] KVM: x86: always expose VIRT_SSBD to guests Paolo Bonzini
2019-08-15 17:14 ` Eduardo Habkost
2019-08-19 15:41 ` Paolo Bonzini
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=1565854883-27019-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.