[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC 2 PATCH 03/16] hw/i386: Introduce X86CPUTopoInfo t
From: |
Babu Moger |
Subject: |
Re: [Qemu-devel] [RFC 2 PATCH 03/16] hw/i386: Introduce X86CPUTopoInfo to contain topology info |
Date: |
Mon, 2 Dec 2019 14:25:56 -0600 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 |
On 10/10/19 10:54 PM, Eduardo Habkost wrote:
> On Fri, Sep 06, 2019 at 07:11:57PM +0000, Moger, Babu wrote:
>> This is an effort to re-arrange few data structure for better
>> readability. Add X86CPUTopoInfo which will have all the topology
>> informations required to build the cpu topology. There is no
>> functional changes.
>>
>> Signed-off-by: Babu Moger <address@hidden>
>> ---
> [...]
>> +typedef struct X86CPUTopoInfo {
>> + unsigned numa_nodes;
>> + unsigned nr_sockets;
>> + unsigned nr_dies;
>> + unsigned nr_cores;
>> + unsigned nr_threads;
>> +} X86CPUTopoInfo;
>
> With more complex topologies, the meaning of each of those fields
> may be ambiguous. e.g.: is nr_cores cores per die, cores per
> ccx, or cores per socket? Maybe we should use this opportunity
> to use more explicit names like threads_per_core, cores_per_die,
> dies_per_socket.
Yes. Changed it to
typedef struct X86CPUTopoInfo {
unsigned nodes_per_pkg;
unsigned dies_per_pkg;
unsigned cores_per_die;
unsigned threads_per_core;
} X86CPUTopoInfo;