qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Tao Su <tao1.su@linux.intel.com>
To: Zhao Liu <zhao1.liu@intel.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Igor Mammedov" <imammedo@redhat.com>,
	"Ewan Hai" <ewanhai-oc@zhaoxin.com>,
	"Xiaoyao Li" <xiaoyao.li@intel.com>, "Tao Su" <tao1.su@intel.com>,
	"Yi Lai" <yi1.lai@intel.com>, "Dapeng Mi" <dapeng1.mi@intel.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH 0/4] i386/cpu: Clean Up Reserved CPUID Leaves for Intel
Date: Mon, 7 Jul 2025 08:55:59 +0800	[thread overview]
Message-ID: <aGsbHwjukIYuF8DX@linux.bj.intel.com> (raw)
In-Reply-To: <20250627035129.2755537-1-zhao1.liu@intel.com>

On Fri, Jun 27, 2025 at 11:51:25AM +0800, Zhao Liu wrote:
> Hi,
> 
> Since the previsor unified cache model series has already introduced a
> new compat property "x-vendor-cpuid-only-v2", it's a chance to once
> again consolidate more vendor-specific CPUIDs.
> 
> I also checked the CPUID leaves currently supported by Intel & AMD and
> found that since the previous "x-vendor-cpuid-only," AMD has already
> cleaned up the Intel-specific CPUIDs quite well.
> 
> As for Intel, the only cleanup needed is for the "extended function
> CPUID" leaves (0x80000000~0x80000008). That's what this series does.
> 
> This series is based on:
> 
> <20250626083105.2581859-1-zhao1.liu@intel.com>
> 
> Or you can find the code at:
> 
> https://gitlab.com/zhao.liu/qemu/-/tree/cache-model-v2.6-rebase-06-23-2025

For the whole series,

Reviewed-by: Tao Su <tao1.su@linux.intel.com>

> 
> Thanks and Best Regards,
> Zhao
> ---
> Zhao Liu (4):
>   i386/cpu: Mark EBX/ECX/EDX in CPUID 0x80000000 leaf as reserved for
>     Intel
>   i386/cpu: Mark CPUID 0x80000007[EBX] as reserved for Intel
>   i386/cpu: Mark ECX/EDX in CPUID 0x80000008 leaf as reserved for Intel
>   i386/cpu: Reorder CPUID leaves in cpu_x86_cpuid()
> 
>  target/i386/cpu.c | 83 ++++++++++++++++++++++++++++-------------------
>  1 file changed, 49 insertions(+), 34 deletions(-)
> 
> -- 
> 2.34.1
> 
> 


      parent reply	other threads:[~2025-07-07  1:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27  3:51 [PATCH 0/4] i386/cpu: Clean Up Reserved CPUID Leaves for Intel Zhao Liu
2025-06-27  3:51 ` [PATCH 1/4] i386/cpu: Mark EBX/ECX/EDX in CPUID 0x80000000 leaf as reserved " Zhao Liu
2025-06-27  5:52   ` Ewan Hai
2025-06-27  8:20   ` Xiaoyao Li
2025-06-27  3:51 ` [PATCH 2/4] i386/cpu: Mark CPUID 0x80000007[EBX] " Zhao Liu
2025-06-27  5:52   ` Ewan Hai
2025-06-27  3:51 ` [PATCH 3/4] i386/cpu: Mark ECX/EDX in CPUID 0x80000008 leaf " Zhao Liu
2025-06-27  5:52   ` Ewan Hai
2025-06-27  8:24   ` Xiaoyao Li
2025-06-30  5:20     ` Zhao Liu
2025-07-01  1:00       ` Xiaoyao Li
2025-06-27  3:51 ` [PATCH 4/4] i386/cpu: Reorder CPUID leaves in cpu_x86_cpuid() Zhao Liu
2025-06-27  8:17 ` [PATCH 0/4] i386/cpu: Clean Up Reserved CPUID Leaves for Intel Xiaoyao Li
2025-07-07  0:55 ` Tao Su [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=aGsbHwjukIYuF8DX@linux.bj.intel.com \
    --to=tao1.su@linux.intel.com \
    --cc=berrange@redhat.com \
    --cc=dapeng1.mi@intel.com \
    --cc=ewanhai-oc@zhaoxin.com \
    --cc=imammedo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tao1.su@intel.com \
    --cc=xiaoyao.li@intel.com \
    --cc=yi1.lai@intel.com \
    --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).