From: Paolo Bonzini <pbonzini@redhat.com>
To: Chao Gao <chao.gao@intel.com>, Zhao Liu <zhao1.liu@intel.com>
Cc: qemu-devel@nongnu.org, jmattson@google.com,
pawan.kumar.gupta@linux.intel.com, jon@nutanix.com,
kvm@vger.kernel.org
Subject: Re: [PATCH] target/i386: Add more features enumerated by CPUID.7.2.EDX
Date: Thu, 10 Oct 2024 15:17:16 +0200 [thread overview]
Message-ID: <9bd5659c-6066-46f9-a096-10f585f8561e@redhat.com> (raw)
In-Reply-To: <ZwY69phzk3GpGvsh@intel.com>
On 10/9/24 10:12, Chao Gao wrote:
>>> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
>>> index 85ef7452c0..18ba958f46 100644
>>> --- a/target/i386/cpu.c
>>> +++ b/target/i386/cpu.c
>>> @@ -1148,8 +1148,8 @@ FeatureWordInfo feature_word_info[FEATURE_WORDS] = {
>>> [FEAT_7_2_EDX] = {
>>> .type = CPUID_FEATURE_WORD,
>>> .feat_names = {
>>> - NULL, NULL, NULL, NULL,
>>> - NULL, "mcdt-no", NULL, NULL,
>>> + "intel-psfd", "ipred-ctrl", "rrsba-ctrl", "ddpd-u",
>>> + "bhi-ctrl", "mcdt-no", NULL, NULL,
>>
>> IIUC, these bits depend on "spec-ctrl", which indicates the presence of
>> IA32_SPEC_CTRL.
>>
>> Then I think we'd better add dependencies in feature_dependencies[].
>
> (+ kvm mailing list)
>
> Thanks for pointing that out. It seems that any of these bits imply the
> presence of IA32_SPEC_CTRL. According to SDM vol4, chapter 2, table 2.2,
> the 'Comment' column for the IA32_SPEC_CTRL MSR states:
>
> If any one of the enumeration conditions for defined bit field positions holds.
>
> So, it might be more appropriate to fix KVM's handling of the
> IA32_SPEC_CTRL MSR (i.e., guest_has_spec_ctrl_msr()).
>
> what do you think?
You're right, the spec-ctrl CPUID feature covers the IBRS bit of
MSR_IA32_SPEC_CTRL and also the IBPB feature of MSR_IA32_PRED_CMD. It
does not specify the existence of MSR_IA32_SPEC_CTRL.
In practice it's probably not a good idea to omit spec-ctrl when passing
other features to the guest that cover that MSR; but the specification
says it's fine.
Paolo
next prev parent reply other threads:[~2024-10-10 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 5:10 [PATCH] target/i386: Add more features enumerated by CPUID.7.2.EDX Chao Gao
2024-10-09 7:47 ` Zhao Liu
2024-10-09 8:12 ` Chao Gao
2024-10-10 13:17 ` Paolo Bonzini [this message]
2024-10-11 4:22 ` Zhao Liu
2024-10-10 13:18 ` 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=9bd5659c-6066-46f9-a096-10f585f8561e@redhat.com \
--to=pbonzini@redhat.com \
--cc=chao.gao@intel.com \
--cc=jmattson@google.com \
--cc=jon@nutanix.com \
--cc=kvm@vger.kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=qemu-devel@nongnu.org \
--cc=zhao1.liu@intel.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).