From: Thomas Huth <thuth@redhat.com>
To: Pierre Morel <pmorel@linux.ibm.com>,
qemu-s390x@nongnu.org, frankja@linux.ibm.com,
Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: qemu-devel@nongnu.org, borntraeger@de.ibm.com,
pasic@linux.ibm.com, richard.henderson@linaro.org,
david@redhat.com, cohuck@redhat.com, mst@redhat.com,
pbonzini@redhat.com, kvm@vger.kernel.org, ehabkost@redhat.com,
marcel.apfelbaum@gmail.com, eblake@redhat.com, armbru@redhat.com,
seiden@linux.ibm.com, nrb@linux.ibm.com, nsg@linux.ibm.com,
berrange@redhat.com, clg@kaod.org
Subject: Re: [PATCH v21 03/20] target/s390x/cpu topology: handle STSI(15) and build the SYSIB
Date: Wed, 12 Jul 2023 22:14:55 +0200 [thread overview]
Message-ID: <6a302f29-9b46-2a5f-c1e2-7f72b38f0f6d@redhat.com> (raw)
In-Reply-To: <b1768b7b-301d-8208-8b31-8ddef378f216@linux.ibm.com>
On 12/07/2023 16.24, Pierre Morel wrote:
>
> On 7/4/23 13:40, Thomas Huth wrote:
>> On 30/06/2023 11.17, Pierre Morel wrote:
>>> On interception of STSI(15.1.x) the System Information Block
>>> (SYSIB) is built from the list of pre-ordered topology entries.
>>>
>>> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
>>> ---
>> ...
>>> diff --git a/target/s390x/cpu.h b/target/s390x/cpu.h
>>> index 7ebd5e05b6..6e7d041b01 100644
>>> --- a/target/s390x/cpu.h
>>> +++ b/target/s390x/cpu.h
>>> @@ -569,6 +569,29 @@ typedef struct SysIB_322 {
>>> } SysIB_322;
>>> QEMU_BUILD_BUG_ON(sizeof(SysIB_322) != 4096);
>>> +/*
>>> + * Topology Magnitude fields (MAG) indicates the maximum number of
>>> + * topology list entries (TLE) at the corresponding nesting level.
>>> + */
>>> +#define S390_TOPOLOGY_MAG 6
>>> +#define S390_TOPOLOGY_MAG6 0
>>> +#define S390_TOPOLOGY_MAG5 1
>>> +#define S390_TOPOLOGY_MAG4 2
>>> +#define S390_TOPOLOGY_MAG3 3
>>> +#define S390_TOPOLOGY_MAG2 4
>>> +#define S390_TOPOLOGY_MAG1 5
>>> +/* Configuration topology */
>>> +typedef struct SysIB_151x {
>>> + uint8_t reserved0[2];
>>> + uint16_t length;
>>> + uint8_t mag[S390_TOPOLOGY_MAG];
>>> + uint8_t reserved1;
>>> + uint8_t mnest;
>>> + uint32_t reserved2;
>>> + char tle[];
>>> +} SysIB_151x;
>>> +QEMU_BUILD_BUG_ON(sizeof(SysIB_151x) != 16);
>>> +
>>> typedef union SysIB {
>>> SysIB_111 sysib_111;
>>> SysIB_121 sysib_121;
>>> @@ -576,9 +599,62 @@ typedef union SysIB {
>>> SysIB_221 sysib_221;
>>> SysIB_222 sysib_222;
>>> SysIB_322 sysib_322;
>>> + SysIB_151x sysib_151x;
>>> } SysIB;
>>> QEMU_BUILD_BUG_ON(sizeof(SysIB) != 4096);
>>> +/*
>>> + * CPU Topology List provided by STSI with fc=15 provides a list
>>> + * of two different Topology List Entries (TLE) types to specify
>>> + * the topology hierarchy.
>>> + *
>>> + * - Container Topology List Entry
>>> + * Defines a container to contain other Topology List Entries
>>> + * of any type, nested containers or CPU.
>>> + * - CPU Topology List Entry
>>> + * Specifies the CPUs position, type, entitlement and polarization
>>> + * of the CPUs contained in the last Container TLE.
>>> + *
>>> + * There can be theoretically up to five levels of containers, QEMU
>>> + * uses only three levels, the drawer's, book's and socket's level.
>>> + *
>>> + * A container with a nesting level (NL) greater than 1 can only
>>> + * contain another container of nesting level NL-1.
>>> + *
>>> + * A container of nesting level 1 (socket), contains as many CPU TLE
>>> + * as needed to describe the position and qualities of all CPUs inside
>>> + * the container.
>>> + * The qualities of a CPU are polarization, entitlement and type.
>>> + *
>>> + * The CPU TLE defines the position of the CPUs of identical qualities
>>> + * using a 64bits mask which first bit has its offset defined by
>>> + * the CPU address orgin field of the CPU TLE like in:
>>> + * CPU address = origin * 64 + bit position within the mask
>>> + *
>>> + */
>>> +/* Container type Topology List Entry */
>>> +typedef struct SysIBTl_container {
>>> + uint8_t nl;
>>> + uint8_t reserved[6];
>>> + uint8_t id;
>>> +} SysIBTl_container;
>>
>> Why mixing CamelCase with underscore-style here? SysIBTlContainer would
>> look more natural, I think?
>
>
> OK, what about SYSIBContainerListEntry ?
Sounds fine!
>
>>
>>> +QEMU_BUILD_BUG_ON(sizeof(SysIBTl_container) != 8);
>>> +
>>> +/* CPU type Topology List Entry */
>>> +typedef struct SysIBTl_cpu {
>>> + uint8_t nl;
>>> + uint8_t reserved0[3];
>>> +#define SYSIB_TLE_POLARITY_MASK 0x03
>>> +#define SYSIB_TLE_DEDICATED 0x04
>>> + uint8_t flags;
>>> + uint8_t type;
>>> + uint16_t origin;
>>> + uint64_t mask;
>>> +} SysIBTl_cpu;
>>
>> dito, maybe better SysIBTlCpu ?
>
>
> What about SysIBCPUListEntry ?
Ack.
Thomas
next prev parent reply other threads:[~2023-07-12 20:15 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 9:17 [PATCH v21 00/20] s390x: CPU Topology Pierre Morel
2023-06-30 9:17 ` [PATCH v21 01/20] s390x/cpu topology: add s390 specifics to CPU topology Pierre Morel
2023-07-18 16:31 ` Nina Schoetterl-Glausch
2023-07-21 11:24 ` Pierre Morel
2023-07-24 10:15 ` Nina Schoetterl-Glausch
2023-07-25 8:43 ` Pierre Morel
2023-06-30 9:17 ` [PATCH v21 02/20] s390x/cpu topology: add topology entries on CPU hotplug Pierre Morel
2023-07-04 10:32 ` Thomas Huth
2023-07-12 11:20 ` Pierre Morel
2023-07-24 20:19 ` Nina Schoetterl-Glausch
2023-07-25 8:44 ` Pierre Morel
2023-06-30 9:17 ` [PATCH v21 03/20] target/s390x/cpu topology: handle STSI(15) and build the SYSIB Pierre Morel
2023-07-04 11:40 ` Thomas Huth
2023-07-04 12:27 ` Thomas Huth
2023-07-12 14:24 ` Pierre Morel
2023-07-12 20:14 ` Thomas Huth [this message]
2023-07-25 15:41 ` Nina Schoetterl-Glausch
2023-07-26 8:11 ` Pierre Morel
2023-07-27 17:31 ` Nina Schoetterl-Glausch
2023-06-30 9:17 ` [PATCH v21 04/20] s390x/sclp: reporting the maximum nested topology entries Pierre Morel
2023-06-30 9:17 ` [PATCH v21 05/20] s390x/cpu topology: resetting the Topology-Change-Report Pierre Morel
2023-07-25 13:43 ` Nina Schoetterl-Glausch
2023-06-30 9:17 ` [PATCH v21 06/20] s390x/cpu topology: interception of PTF instruction Pierre Morel
2023-07-04 12:16 ` Thomas Huth
2023-07-12 14:40 ` Pierre Morel
2023-06-30 9:17 ` [PATCH v21 07/20] target/s390x/cpu topology: activate CPU topology Pierre Morel
2023-06-30 9:17 ` [PATCH v21 08/20] qapi/s390x/cpu topology: set-cpu-topology qmp command Pierre Morel
2023-07-04 12:53 ` Thomas Huth
2023-07-12 14:45 ` Pierre Morel
2023-07-18 7:54 ` Nina Schoetterl-Glausch
2023-07-18 12:25 ` Pierre Morel
2023-06-30 9:17 ` [PATCH v21 09/20] machine: adding s390 topology to query-cpu-fast Pierre Morel
2023-07-04 12:55 ` Thomas Huth
2023-07-12 15:44 ` Pierre Morel
2023-06-30 9:17 ` [PATCH v21 10/20] machine: adding s390 topology to info hotpluggable-cpus Pierre Morel
2023-07-04 12:59 ` Thomas Huth
2023-07-12 16:02 ` Pierre Morel
2023-06-30 9:17 ` [PATCH v21 11/20] qapi/s390x/cpu topology: CPU_POLARIZATION_CHANGE qapi event Pierre Morel
2023-07-04 13:04 ` Thomas Huth
2023-07-12 16:05 ` Pierre Morel
2023-07-18 7:59 ` Nina Schoetterl-Glausch
2023-07-18 12:34 ` Pierre Morel
2023-06-30 9:17 ` [PATCH v21 12/20] qapi/s390x/cpu topology: query-cpu-polarization qmp command Pierre Morel
2023-07-05 7:58 ` Thomas Huth
2023-07-12 16:12 ` Pierre Morel
2023-07-26 11:54 ` Nina Schoetterl-Glausch
2023-06-30 9:17 ` [PATCH v21 13/20] docs/s390x/cpu topology: document s390x cpu topology Pierre Morel
2023-07-05 8:41 ` Thomas Huth
2023-07-12 16:27 ` Pierre Morel
2023-06-30 9:17 ` [PATCH v21 14/20] tests/avocado: s390x cpu topology core Pierre Morel
2023-07-04 13:14 ` Thomas Huth
2023-07-19 9:24 ` Pierre Morel
2023-07-12 20:00 ` Nina Schoetterl-Glausch
2023-07-19 11:05 ` Pierre Morel
2023-06-30 9:17 ` [PATCH v21 15/20] tests/avocado: s390x cpu topology polarisation Pierre Morel
2023-07-05 8:53 ` Thomas Huth
2023-07-19 11:35 ` Pierre Morel
2023-06-30 9:17 ` [PATCH v21 16/20] tests/avocado: s390x cpu topology entitlement tests Pierre Morel
2023-07-05 10:22 ` Thomas Huth
2023-07-12 19:37 ` Nina Schoetterl-Glausch
2023-07-12 20:11 ` Thomas Huth
2023-07-14 16:30 ` Nina Schoetterl-Glausch
2023-07-19 14:08 ` Pierre Morel
2023-07-19 14:13 ` Nina Schoetterl-Glausch
2023-07-19 15:34 ` Pierre Morel
2023-06-30 9:17 ` [PATCH v21 17/20] tests/avocado: s390x cpu topology test dedicated CPU Pierre Morel
2023-07-19 14:09 ` Pierre Morel
2023-06-30 9:17 ` [PATCH v21 18/20] tests/avocado: s390x cpu topology test socket full Pierre Morel
2023-07-05 10:26 ` Thomas Huth
2023-07-19 14:21 ` Pierre Morel
2023-06-30 9:17 ` [PATCH v21 19/20] tests/avocado: s390x cpu topology dedicated errors Pierre Morel
2023-07-05 10:28 ` Thomas Huth
2023-07-19 14:21 ` Pierre Morel
2023-06-30 9:17 ` [PATCH v21 20/20] tests/avocado: s390x cpu topology bad move Pierre Morel
2023-07-05 10:32 ` Thomas Huth
2023-07-19 14:23 ` Pierre Morel
2023-07-05 10:02 ` [PATCH v21 00/20] s390x: CPU Topology Thomas Huth
2023-07-19 15:27 ` Pierre Morel
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=6a302f29-9b46-2a5f-c1e2-7f72b38f0f6d@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=clg@kaod.org \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=nrb@linux.ibm.com \
--cc=nsg@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=seiden@linux.ibm.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).