From: Ewan Hai <ewanhai-oc@zhaoxin.com>
To: Zhao Liu <zhao1.liu@intel.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Babu Moger" <babu.moger@amd.com>,
"Xiaoyao Li" <xiaoyao.li@intel.com>,
"Tejus GK" <tejus.gk@nutanix.com>,
"Jason Zeng" <jason.zeng@intel.com>,
"Manish Mishra" <manish.mishra@nutanix.com>,
"Tao Su" <tao1.su@intel.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org, cobechen@zhaoxin.com,
yeeli@zhaoxin.com, MaryFeng@zhaoxin.com, Runaguo@zhaoxin.com,
Xanderchen@zhaoxin.com
Subject: Re: [RFC 01/10] i386/cpu: Mark CPUID[0x80000005] as reserved for Intel
Date: Wed, 25 Jun 2025 18:05:46 +0800 [thread overview]
Message-ID: <4833e1be-b38d-4f80-abb7-aff2782efcfb@zhaoxin.com> (raw)
In-Reply-To: <aFu/EED7BNJgIXqH@intel.com>
On 6/25/25 5:19 PM, Zhao Liu wrote:
>
>
> Just want to confirm with the "lines_per_tag" field, which is related
> about how to handle current "assert(lines_per_tag > 0)":
>
>> --- patch prototype start ---
>>
>> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
>> index 7b223642ba..8a17e5ffe9 100644
>> --- a/target/i386/cpu.c
>> +++ b/target/i386/cpu.c
>> @@ -2726,6 +2726,66 @@ static const CPUCaches xeon_srf_cache_info = {
>> },
>> };
>>
>> +static const CPUCaches yongfeng_cache_info = {
>> + .l1d_cache = &(CPUCacheInfo) {
>> + .type = DATA_CACHE,
>> + .level = 1,
>> + .size = 32 * KiB,
>> + .line_size = 64,
>> + .associativity = 8,
>> + .partitions = 1,
>> + .sets = 64,
>> + .lines_per_tag = 1,
>
> This fits AMD APM, and is fine.
>
>> + .inclusive = false,
>> + .self_init = true,
>> + .no_invd_sharing = false,
>> + .share_level = CPU_TOPOLOGY_LEVEL_CORE,
>> + },
>> + .l1i_cache = &(CPUCacheInfo) {
>> + .type = INSTRUCTION_CACHE,
>> + .level = 1,
>> + .size = 64 * KiB,
>> + .line_size = 64,
>> + .associativity = 16,
>> + .partitions = 1,
>> + .sets = 64,
>> + .lines_per_tag = 1,
>
> Fine, too.
>
>> + .inclusive = false,
>> + .self_init = true,
>> + .no_invd_sharing = false,
>> + .share_level = CPU_TOPOLOGY_LEVEL_CORE,
>> + },
>> + .l2_cache = &(CPUCacheInfo) {
>> + .type = UNIFIED_CACHE,
>> + .level = 2,
>> + .size = 256 * KiB,
>> + .line_size = 64,
>> + .associativity = 8,
>> + .partitions = 1,
>> + .sets = 512,
>> + .lines_per_tag = 1,
>
> SDM reserves this field:
>
> For 0x80000006 ECX:
>
> Bits 11-08: Reserved.
>
> So I think this field should be 0, to align with "Reserved".
I agree. For Zhaoxin, the "lines-per-tag" field appears only in CPUID leaf
0x80000005. Because Zhaoxin follows AMD behavior on this leaf, and the AMD
manual states that it reports L1 cache/TLB information, so any "lines-per-tag"
value for levels other than L1 should be omitted or set to zero.
>
> In this patch:
>
> https://lore.kernel.org/qemu-devel/20250620092734.1576677-9-zhao1.liu@intel.com/
>
> I add an argument (lines_per_tag_supported) in encode_cache_cpuid80000006(),
> and for the case that lines_per_tag_supported=false, I assert
> "lines_per_tag == 0" to align with "Reserved".
>
>> + .inclusive = true,
>> + .self_init = true,
>> + .no_invd_sharing = false,
>> + .share_level = CPU_TOPOLOGY_LEVEL_CORE,
>> + },
>> + .l3_cache = &(CPUCacheInfo) {
>> + .type = UNIFIED_CACHE,
>> + .level = 3,
>> + .size = 8 * MiB,
>> + .line_size = 64,
>> + .associativity = 16,
>> + .partitions = 1,
>> + .sets = 8192,
>> + .lines_per_tag = 1,
>
> The 0x80000006 EDX is also reserved in SDM. So I think this field should
> be 0, too.
>
> Do you agree?
Ditto.>
>> + .self_init = true,
>> + .inclusive = true,
>> + .no_invd_sharing = true,
>> + .complex_indexing = false,
>> + .share_level = CPU_TOPOLOGY_LEVEL_DIE,
>> + },
>> +};
>> +
next prev parent reply other threads:[~2025-06-26 0:25 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 11:46 [RFC 00/10] i386/cpu: Cache CPUID fixup, Intel cache model & topo CPUID enhencement Zhao Liu
2025-04-23 11:46 ` [RFC 01/10] i386/cpu: Mark CPUID[0x80000005] as reserved for Intel Zhao Liu
2025-04-23 13:05 ` Xiaoyao Li
2025-04-24 2:52 ` Zhao Liu
2025-04-24 13:44 ` Ewan Hai
2025-04-25 9:39 ` Zhao Liu
2025-05-26 8:35 ` Ewan Hai
2025-05-27 9:15 ` Zhao Liu
2025-05-27 9:56 ` Ewan Hai
2025-06-24 7:22 ` Zhao Liu
2025-06-24 11:04 ` Ewan Hai
2025-06-25 3:03 ` Zhao Liu
2025-06-25 2:54 ` Ewan Hai
2025-06-25 9:19 ` Zhao Liu
2025-06-25 10:05 ` Ewan Hai [this message]
2025-04-23 11:46 ` [RFC 02/10] i386/cpu: Fix CPUID[0x80000006] for Intel CPU Zhao Liu
2025-04-23 11:46 ` [RFC 03/10] i386/cpu: Introduce cache model for SierraForest Zhao Liu
2025-04-23 11:46 ` [RFC 04/10] i386/cpu: Introduce cache model for GraniteRapids Zhao Liu
2025-04-23 11:46 ` [RFC 05/10] i386/cpu: Introduce cache model for SapphireRapids Zhao Liu
2025-04-24 4:54 ` Tejus GK
2025-04-24 6:53 ` Zhao Liu
2025-04-23 11:46 ` [RFC 06/10] i386/cpu: Introduce enable_cpuid_0x1f to force exposing CPUID 0x1f Zhao Liu
2025-05-13 12:45 ` Igor Mammedov
2025-05-14 15:23 ` Zhao Liu
2025-05-15 6:43 ` Xiaoyao Li
2025-04-23 11:46 ` [RFC 07/10] i386/cpu: Add a "cpuid-0x1f" property Zhao Liu
2025-04-23 11:47 ` [RFC 08/10] i386/cpu: Enable 0x1f leaf for SierraForest by default Zhao Liu
2025-04-23 11:47 ` [RFC 09/10] i386/cpu: Enable 0x1f leaf for GraniteRapids " Zhao Liu
2025-04-23 11:47 ` [RFC 10/10] i386/cpu: Enable 0x1f leaf for SapphireRapids " Zhao Liu
2025-04-24 6:57 ` [RFC 00/10] i386/cpu: Cache CPUID fixup, Intel cache model & topo CPUID enhencement Zhao Liu
2025-05-26 10:52 ` Ewan Hai
2025-05-27 9:19 ` Zhao Liu
2025-05-27 9:58 ` Ewan Hai
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=4833e1be-b38d-4f80-abb7-aff2782efcfb@zhaoxin.com \
--to=ewanhai-oc@zhaoxin.com \
--cc=MaryFeng@zhaoxin.com \
--cc=Runaguo@zhaoxin.com \
--cc=Xanderchen@zhaoxin.com \
--cc=babu.moger@amd.com \
--cc=berrange@redhat.com \
--cc=cobechen@zhaoxin.com \
--cc=imammedo@redhat.com \
--cc=jason.zeng@intel.com \
--cc=kvm@vger.kernel.org \
--cc=manish.mishra@nutanix.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tao1.su@intel.com \
--cc=tejus.gk@nutanix.com \
--cc=xiaoyao.li@intel.com \
--cc=yeeli@zhaoxin.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).