[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F]
|
From: |
Zhao Liu |
|
Subject: |
Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F] |
|
Date: |
Mon, 15 Jan 2024 14:35:31 +0800 |
On Mon, Jan 15, 2024 at 02:11:17PM +0800, Xiaoyao Li wrote:
> Date: Mon, 15 Jan 2024 14:11:17 +0800
> From: Xiaoyao Li <xiaoyao.li@intel.com>
> Subject: Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F]
>
> On 1/15/2024 2:12 PM, Zhao Liu wrote:
> > Hi Xiaoyao,
> >
> > On Mon, Jan 15, 2024 at 12:34:12PM +0800, Xiaoyao Li wrote:
> > > Date: Mon, 15 Jan 2024 12:34:12 +0800
> > > From: Xiaoyao Li <xiaoyao.li@intel.com>
> > > Subject: Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F]
> > >
> > > > Yes, I think it's time to move to default 0x1f.
> > >
> > > we don't need to do so until it's necessary.
> >
> > Recent and future machines all support 0x1f, and at least SDM has
> > emphasized the preferred use of 0x1f.
>
> The preference is the guideline for software e.g., OS. QEMU doesn't need to
> emulate cpuid leaf 0x1f to guest if there is only smt and core level.
Please, QEMU is emulating hardware not writing software. Is there any
reason why we shouldn't emulate new and generic hardware behaviors and
stick with the old ones?
> because in this case, they are exactly the same in leaf 0xb and 0x1f. we don't
> need to bother advertising the duplicate data.
You can't "define" the same 0x0b and 0x1f as duplicates. SDM doesn't
have such the definition.
Regards,
Zhao
- Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F], (continued)
- Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F], Yuan Yao, 2024/01/14
- Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F], Zhao Liu, 2024/01/14
- Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F], Xiaoyao Li, 2024/01/14
- Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F], Yuan Yao, 2024/01/15
- Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F], Zhao Liu, 2024/01/15
- Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F], Yuan Yao, 2024/01/15
- Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F], Zhao Liu, 2024/01/15
- Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F], Yuan Yao, 2024/01/15
- Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F], Zhao Liu, 2024/01/15
- Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F], Xiaoyao Li, 2024/01/15
- Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F],
Zhao Liu <=
- Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F], Xiaoyao Li, 2024/01/15
- Re: [PATCH v7 08/16] i386: Expose module level in CPUID[0x1F], Zhao Liu, 2024/01/15
[PATCH v7 09/16] i386: Support module_id in X86CPUTopoIDs, Zhao Liu, 2024/01/08
[PATCH v7 13/16] i386: Add cache topology info in CPUCacheInfo, Zhao Liu, 2024/01/08
[PATCH v7 11/16] tests: Add test case of APIC ID for module level parsing, Zhao Liu, 2024/01/08
[PATCH v7 14/16] i386: Use CPUCacheInfo.share_level to encode CPUID[4], Zhao Liu, 2024/01/08