From: Jim Mattson <jmattson@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
kvm list <kvm@vger.kernel.org>,
jmattson@redhat.com, Eduardo Habkost <ehabkost@redhat.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH 1/3] KVM: x86: fix reporting of AMD speculation bug CPUID leaf
Date: Wed, 21 Aug 2019 12:45:29 -0700 [thread overview]
Message-ID: <CALMp9eQoHLngzb5v9aqxpJ39OszXLjdm+sWbHdeOk2JaPofv5Q@mail.gmail.com> (raw)
In-Reply-To: <1566376002-17121-2-git-send-email-pbonzini@redhat.com>
On Wed, Aug 21, 2019 at 1:27 AM Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> The AMD_* bits have to be set from the vendor-independent
> feature and bug flags, because KVM_GET_SUPPORTED_CPUID does not care
> about the vendor and they should be set on Intel processors as well.
> On top of this, SSBD, STIBP and AMD_SSB_NO bit were not set, and
> VIRT_SSBD does not have to be added manually because it is a
> cpufeature that comes directly from the host's CPUID bit.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Jim Mattson <jmattson@google.com>
next prev parent reply other threads:[~2019-08-21 19:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 8:26 [PATCH v2 0/3] KVM: x86: fixes for speculation bug feature reporting Paolo Bonzini
2019-08-21 8:26 ` [PATCH 1/3] KVM: x86: fix reporting of AMD speculation bug CPUID leaf Paolo Bonzini
2019-08-21 19:45 ` Jim Mattson [this message]
2019-08-22 18:46 ` Konrad Rzeszutek Wilk
2019-11-30 23:27 ` Eric Biggers
2019-12-09 17:55 ` Eric Biggers
2019-12-13 22:27 ` Eduardo Habkost
2019-08-21 8:26 ` [PATCH 2/3] KVM: x86: always expose VIRT_SSBD to guests Paolo Bonzini
2019-08-21 19:47 ` Jim Mattson
2019-08-22 18:44 ` Konrad Rzeszutek Wilk
2019-10-01 22:16 ` Eduardo Habkost
2019-10-06 16:08 ` Paolo Bonzini
2019-08-21 8:26 ` [PATCH 3/3] KVM: x86: use Intel speculation bugs and features as derived in generic x86 code Paolo Bonzini
2019-08-21 19:48 ` Jim Mattson
2019-08-22 18:45 ` Konrad Rzeszutek Wilk
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=CALMp9eQoHLngzb5v9aqxpJ39OszXLjdm+sWbHdeOk2JaPofv5Q@mail.gmail.com \
--to=jmattson@google.com \
--cc=ehabkost@redhat.com \
--cc=jmattson@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).