qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Zhao Liu <zhao1.liu@intel.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Cameron Esfahani <dirty@apple.com>,
	Roman Bolshakov <rbolshakov@ddn.com>,
	Phil Dennis-Jordan <phil@philjordan.eu>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] i386/hvf: Make CPUID_HT supported
Date: Thu, 15 May 2025 16:17:28 +0800	[thread overview]
Message-ID: <aCWjGFFlKqwOyY0/@intel.com> (raw)
In-Reply-To: <20250514031652.838763-3-xiaoyao.li@intel.com>

On Tue, May 13, 2025 at 11:16:52PM -0400, Xiaoyao Li wrote:
> Date: Tue, 13 May 2025 23:16:52 -0400
> From: Xiaoyao Li <xiaoyao.li@intel.com>
> Subject: [PATCH 2/2] i386/hvf: Make CPUID_HT supported
> X-Mailer: git-send-email 2.43.0
> 
> Since Commit c6bd2dd63420 ("i386/cpu: Set up CPUID_HT in
> x86_cpu_expand_features() instead of cpu_x86_cpuid()"), CPUID_HT will be
> set in env->features[] in x86_cpu_expand_features() when vcpus >= 2.
> 
> Later in x86_cpu_filter_features() it will check against the HVF
> supported bits. It will trigger the warning like
> 
>     qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.ht [bit 28]
> 
> Add CPUID_HT to HVF supported CPUID bits to fix it.
> 
> Signed-off-by: Xiaoyao Li <xiaoyao.li@intel.com>
> ---
> Note, the issue is totally by my analysis (which should be the same as
> the TCG warnings) because I don't have HVF environment to verify it.
> 
> If would be helpful if anyone can help reproduce it and test the patch
> in HVF environment.

Ah, I found someone has reported a bug on HVF. In his log, there's the
ht warning:

https://gitlab.com/qemu-project/qemu/-/issues/2938

But I don't know if this fix can help on his bug...let's wait for his
feedback.

> ---
>  target/i386/hvf/x86_cpuid.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Anyway, this fix is fine for me, so,

Reviewed-by: Zhao Liu <zhao1.liu@intel.com>



  reply	other threads:[~2025-05-15  7:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-14  3:16 [PATCH 0/2] Fixes for TCG/HVF warning of CPUID_HT and CPUID_EXT3_CMP_LEG Xiaoyao Li
2025-05-14  3:16 ` [PATCH 1/2] i386/tcg: Make CPUID_HT and CPUID_EXT3_CMP_LEG supported Xiaoyao Li
2025-05-15  7:53   ` Zhao Liu
2025-05-14  3:16 ` [PATCH 2/2] i386/hvf: Make CPUID_HT supported Xiaoyao Li
2025-05-15  8:17   ` Zhao Liu [this message]
2025-05-16  3:17     ` Zhao Liu
2025-05-22 11:27 ` [PATCH 0/2] Fixes for TCG/HVF warning of CPUID_HT and CPUID_EXT3_CMP_LEG Michael Tokarev

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=aCWjGFFlKqwOyY0/@intel.com \
    --to=zhao1.liu@intel.com \
    --cc=dirty@apple.com \
    --cc=pbonzini@redhat.com \
    --cc=phil@philjordan.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=rbolshakov@ddn.com \
    --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).