From: Farrah Chen <farrah.chen@intel.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>
Cc: mtosatti@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org,
farrah.chen@intel.com
Subject: Re: [PATCH] targer/i386/cpu: Fix CPUID_HT exposure
Date: Thu, 12 Oct 2023 17:39:08 +0800 [thread overview]
Message-ID: <ZSe84OlMUgCKkevt@emr-120485.sh.intel.com> (raw)
In-Reply-To: <20231010060539.210258-1-xiaoyao.li@intel.com>
On 2023-10-10 at 02:05:39 -0400, Xiaoyao Li wrote:
> When explicitly booting a multiple vcpus vm with "-cpu +ht", it gets
> warning of
>
> warning: host doesn't support requested feature: CPUID.01H:EDX.ht [bit 28]
>
> Make CPUID_HT as supported unconditionally can resolve the warning.
> However it introduces another issue that it also expose CPUID_HT to
> guest when "-cpu host/max" with only 1 vcpu. To fix this, need mark
> CPUID_HT as the no_autoenable_flags.
>
> Signed-off-by: Xiaoyao Li <xiaoyao.li@intel.com>
> ---
> target/i386/cpu.c | 1 +
> target/i386/kvm/kvm.c | 2 ++
> 2 files changed, 3 insertions(+)
>
> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> index cec5d2b7b65e..32c077455f04 100644
> --- a/target/i386/cpu.c
> +++ b/target/i386/cpu.c
> @@ -778,6 +778,7 @@ FeatureWordInfo feature_word_info[FEATURE_WORDS] = {
> },
> .cpuid = {.eax = 1, .reg = R_EDX, },
> .tcg_features = TCG_FEATURES,
> + .no_autoenable_flags = CPUID_HT,
> },
> [FEAT_1_ECX] = {
> .type = CPUID_FEATURE_WORD,
> diff --git a/target/i386/kvm/kvm.c b/target/i386/kvm/kvm.c
> index f6c7f7e26869..ab72bcdfad13 100644
> --- a/target/i386/kvm/kvm.c
> +++ b/target/i386/kvm/kvm.c
> @@ -373,6 +373,8 @@ uint32_t kvm_arch_get_supported_cpuid(KVMState *s, uint32_t function,
> if (function == 1 && reg == R_EDX) {
> /* KVM before 2.6.30 misreports the following features */
> ret |= CPUID_MTRR | CPUID_PAT | CPUID_MCE | CPUID_MCA;
> + /* KVM never reports CPUID_HT but QEMU can support when vcpus > 1 */
> + ret |= CPUID_HT;
> } else if (function == 1 && reg == R_ECX) {
> /* We can set the hypervisor flag, even if KVM does not return it on
> * GET_SUPPORTED_CPUID
Tested-by: Farrah Chen <farrah.chen@intel.com>
>
> base-commit: cea3ea670fe265421131aad90c36fbb87bc4d206
> --
> 2.34.1
>
>
prev parent reply other threads:[~2023-10-12 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 6:05 [PATCH] targer/i386/cpu: Fix CPUID_HT exposure Xiaoyao Li
2023-10-10 14:20 ` Paolo Bonzini
2023-10-12 9:39 ` Farrah Chen [this message]
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=ZSe84OlMUgCKkevt@emr-120485.sh.intel.com \
--to=farrah.chen@intel.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiaoyao.li@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).