From: Wei Wang <wei.w.wang@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Cc: jmattson@google.com, liran.alon@oracle.com
Subject: Re: [PATCH RFC] x86/kvm: expose the CPUID of SPEC_CTRL and STIBP to guests
Date: Tue, 09 Jan 2018 17:15:03 +0800 [thread overview]
Message-ID: <5A548817.2040100@intel.com> (raw)
In-Reply-To: <e0327322-7883-f19e-76ef-2f5f03796a94@redhat.com>
On 01/09/2018 04:39 PM, Paolo Bonzini wrote:
> On 09/01/2018 07:25, Wei Wang wrote:
>> This patch shows an alternative approach to the one posted here:
>> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1580364.html
>>
>> The advantages are
>> 1) Simpler;
>> 2) More reasonable because this is used to fill the hardware security
>> hole, for all the x86 cpus that physically support the two CPUIDs,
>> which means the hole already exists physically. All the VMs should
>> use this feature no matter what CPU model they are using. So, exposing
>> the two CPUIDs as long as they are physically supported by the hardware,
>> and this doesn't require the QEMU side hardcode as usual.
>>
>> When the related feature bits are added to the kernel, and we can simply
>> change it to:
>> best->edx |= F(SPEC_CTRL) | F(PRED_CMD);
> Is this meant to replace the whole series or just patch 1/7? The
> functions in patch 1/7 are used later by vmx.c and svm.c.
>
The pointer should have pointed to 7/7 (not 1/7). Just patch 7/7 actually.
Best,
Wei
next prev parent reply other threads:[~2018-01-09 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 6:25 [PATCH RFC] x86/kvm: expose the CPUID of SPEC_CTRL and STIBP to guests Wei Wang
2018-01-09 8:39 ` Paolo Bonzini
2018-01-09 9:15 ` Wei Wang [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-09 8:43 Liran Alon
2018-01-09 8:44 ` Paolo Bonzini
2018-01-09 9:16 ` Wei Wang
2018-01-09 9:24 ` Paolo Bonzini
2018-01-09 17:07 ` Jim Mattson
2018-01-09 8:52 Liran Alon
2018-01-09 8:57 ` 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=5A548817.2040100@intel.com \
--to=wei.w.wang@intel.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@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