From: Pierre Morel <pmorel@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>, qemu-s390x@nongnu.org
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,
frankja@linux.ibm.com, berrange@redhat.com, clg@kaod.org
Subject: Re: [PATCH v20 01/21] s390x/cpu topology: add s390 specifics to CPU topology
Date: Fri, 28 Apr 2023 14:27:18 +0200 [thread overview]
Message-ID: <9ffdbd31-061c-619d-8902-69782ceed7a9@linux.ibm.com> (raw)
In-Reply-To: <45e09800-6a47-0372-5244-16e2dc72370d@redhat.com>
On 4/27/23 10:04, Thomas Huth wrote:
> On 25/04/2023 18.14, Pierre Morel wrote:
>> S390 adds two new SMP levels, drawers and books to the CPU
>> topology.
>> The S390 CPU have specific topology features like dedication
>> and entitlement to give to the guest indications on the host
>> vCPUs scheduling and help the guest take the best decisions
>> on the scheduling of threads on the vCPUs.
>>
>> Let us provide the SMP properties with books and drawers levels
>> and S390 CPU with dedication and entitlement,
>>
>> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
>> ---
> ...> diff --git a/qapi/machine-target.json b/qapi/machine-target.json
>> index 2e267fa458..42a6a40333 100644
>> --- a/qapi/machine-target.json
>> +++ b/qapi/machine-target.json
>> @@ -342,3 +342,15 @@
>> 'TARGET_S390X',
>> 'TARGET_MIPS',
>> 'TARGET_LOONGARCH64' ] } }
>> +
>> +##
>> +# @CpuS390Polarization:
>> +#
>> +# An enumeration of cpu polarization that can be assumed by a virtual
>> +# S390 CPU
>> +#
>> +# Since: 8.1
>> +##
>> +{ 'enum': 'CpuS390Polarization',
>> + 'prefix': 'S390_CPU_POLARIZATION',
>> + 'data': [ 'horizontal', 'vertical' ] }
>
> It seems like you don't need this here yet ... I think you likely
> could also introduce it in a later patch instead (patch 11 seems the
> first one that needs this?)
>
> Also, would a " 'if': 'TARGET_S390X' " be possible here, too?
Yes, I will shift this to patch 11.
>
>> diff --git a/hw/core/machine-smp.c b/hw/core/machine-smp.c
>> index c3dab007da..77bee06304 100644
>> --- a/hw/core/machine-smp.c
>> +++ b/hw/core/machine-smp.c
>> @@ -30,8 +30,19 @@ static char *cpu_hierarchy_to_string(MachineState
>> *ms)
>> {
>> MachineClass *mc = MACHINE_GET_CLASS(ms);
>> GString *s = g_string_new(NULL);
>> + const char *multiply = " * ", *prefix = "";
>> - g_string_append_printf(s, "sockets (%u)", ms->smp.sockets);
>> + if (mc->smp_props.drawers_supported) {
>> + g_string_append_printf(s, "drawers (%u)", ms->smp.drawers);
>> + prefix = multiply;
>
> That "prefix" stuff looks complicated ... why don't you simply add the
> "*" at the end of the strings:
>
> g_string_append_printf(s, "drawers (%u) * ",
> ms->smp.drawers);
>
> ?
Right, I did not think enough when I made this change.
>
>> + }
>> +
>> + if (mc->smp_props.books_supported) {
>> + g_string_append_printf(s, "%sbooks (%u)", prefix,
>> ms->smp.books);
>> + prefix = multiply;
>> + }
>> +
>> + g_string_append_printf(s, "%ssockets (%u)", prefix,
>> ms->smp.sockets);
>
> ... it's followed by "sockets" here anyway, so adding the " * " at the
> end of the strings above should be fine.
yes
>
>> {
>> MachineClass *mc = MACHINE_GET_CLASS(ms);
>> unsigned cpus = config->has_cpus ? config->cpus : 0;
>> + unsigned drawers = config->has_drawers ? config->drawers : 0;
>> + unsigned books = config->has_books ? config->books : 0;
>> unsigned sockets = config->has_sockets ? config->sockets : 0;
>> unsigned dies = config->has_dies ? config->dies : 0;
>> unsigned clusters = config->has_clusters ? config->clusters : 0;
>> @@ -85,6 +98,8 @@ void machine_parse_smp_config(MachineState *ms,
>> * explicit configuration like "cpus=0" is not allowed.
>> */
>> if ((config->has_cpus && config->cpus == 0) ||
>> + (config->has_drawers && config->drawers == 0) ||
>> + (config->has_books && config->books == 0) ||
>> (config->has_sockets && config->sockets == 0) ||
>> (config->has_dies && config->dies == 0) ||
>> (config->has_clusters && config->clusters == 0) ||
>> @@ -111,6 +126,19 @@ void machine_parse_smp_config(MachineState *ms,
>> dies = dies > 0 ? dies : 1;
>> clusters = clusters > 0 ? clusters : 1;
>> + if (!mc->smp_props.books_supported && books > 1) {
>> + error_setg(errp, "books not supported by this machine's CPU
>> topology");
>> + return;
>> + }
>> + books = books > 0 ? books : 1;
>
> Could be shortened to: book = books ?: 1;
I always forgot that Elvis is not dead
>
>> + if (!mc->smp_props.drawers_supported && drawers > 1) {
>> + error_setg(errp,
>> + "drawers not supported by this machine's CPU
>> topology");
>> + return;
>> + }
>> + drawers = drawers > 0 ? drawers : 1;
>
> Could be shortened to: drawers = drawers ?: 1;
yes
>
>> /* compute missing values based on the provided ones */
>> if (cpus == 0 && maxcpus == 0) {
>> sockets = sockets > 0 ? sockets : 1;
>> @@ -124,33 +152,41 @@ void machine_parse_smp_config(MachineState *ms,
>> if (sockets == 0) {
>> cores = cores > 0 ? cores : 1;
>> threads = threads > 0 ? threads : 1;
>> - sockets = maxcpus / (dies * clusters * cores *
>> threads);
>> + sockets = maxcpus /
>> + (drawers * books * dies * clusters * cores
>> * threads);
>> } else if (cores == 0) {
>> threads = threads > 0 ? threads : 1;
>> - cores = maxcpus / (sockets * dies * clusters *
>> threads);
>> + cores = maxcpus /
>> + (drawers * books * sockets * dies * clusters
>> * threads);
>> }
>
> (not very important, but I wonder whether we should maybe disallow
> "prefer_sockets" with drawers and books instead of updating the
> calculation here - since prefer_sockets should only occur on old
> machine types)
It is OK for me. The contra argument would be that for balancing it is
nicer.
But as you like, it makes less code and we can add it later if we ever
set prefer_socket = true again, which is very uncertain.
>
>> } else {
>> /* prefer cores over sockets since 6.2 */
>> if (cores == 0) {
>> sockets = sockets > 0 ? sockets : 1;
>> threads = threads > 0 ? threads : 1;
>> - cores = maxcpus / (sockets * dies * clusters *
>> threads);
>> + cores = maxcpus /
>> + (drawers * books * sockets * dies * clusters
>> * threads);
>> } else if (sockets == 0) {
>> threads = threads > 0 ? threads : 1;
>> - sockets = maxcpus / (dies * clusters * cores *
>> threads);
>> + sockets = maxcpus /
>> + (drawers * books * dies * clusters * cores
>> * threads);
>> }
>> }
>
> Thomas
>
Thanks Thomas.
Regards,
Pierre
next prev parent reply other threads:[~2023-04-28 12:29 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 16:14 [PATCH v20 00/21] s390x: CPU Topology Pierre Morel
2023-04-25 16:14 ` [PATCH v20 01/21] s390x/cpu topology: add s390 specifics to CPU topology Pierre Morel
2023-04-27 8:04 ` Thomas Huth
2023-04-28 12:27 ` Pierre Morel [this message]
2023-05-03 9:36 ` Pierre Morel
2023-05-03 9:54 ` Thomas Huth
2023-05-03 11:17 ` Pierre Morel
2023-05-02 12:05 ` Cédric Le Goater
2023-05-02 13:48 ` Cédric Le Goater
2023-05-03 7:23 ` Pierre Morel
2023-04-25 16:14 ` [PATCH v20 02/21] s390x/cpu topology: add topology entries on CPU hotplug Pierre Morel
2023-04-27 13:38 ` Thomas Huth
2023-04-28 12:35 ` Pierre Morel
2023-05-03 9:12 ` Thomas Huth
2023-05-03 10:23 ` Cédric Le Goater
2023-06-21 13:48 ` Pierre Morel
2023-05-02 12:30 ` Cédric Le Goater
2023-05-03 7:21 ` Pierre Morel
2023-05-03 11:23 ` Cédric Le Goater
2023-04-25 16:14 ` [PATCH v20 03/21] target/s390x/cpu topology: handle STSI(15) and build the SYSIB Pierre Morel
2023-04-27 17:01 ` Thomas Huth
2023-04-28 12:42 ` Pierre Morel
2023-05-02 17:22 ` Nina Schoetterl-Glausch
2023-05-03 8:43 ` Pierre Morel
2023-05-03 13:01 ` Nina Schoetterl-Glausch
2023-04-25 16:14 ` [PATCH v20 04/21] s390x/sclp: reporting the maximum nested topology entries Pierre Morel
2023-04-25 16:14 ` [PATCH v20 05/21] s390x/cpu topology: resetting the Topology-Change-Report Pierre Morel
2023-04-25 16:14 ` [PATCH v20 06/21] s390x/cpu topology: interception of PTF instruction Pierre Morel
2023-05-04 11:03 ` Nina Schoetterl-Glausch
2023-05-05 9:34 ` Pierre Morel
2023-04-25 16:14 ` [PATCH v20 07/21] target/s390x/cpu topology: activate CPU topology Pierre Morel
2023-04-25 16:14 ` [PATCH v20 08/21] qapi/s390x/cpu topology: set-cpu-topology qmp command Pierre Morel
2023-05-08 19:42 ` Nina Schoetterl-Glausch
2023-05-09 8:50 ` Pierre Morel
2023-04-25 16:14 ` [PATCH v20 09/21] machine: adding s390 topology to query-cpu-fast Pierre Morel
2023-06-12 7:55 ` Cédric Le Goater
2023-06-21 12:50 ` Pierre Morel
2023-04-25 16:14 ` [PATCH v20 10/21] machine: adding s390 topology to info hotpluggable-cpus Pierre Morel
2023-05-08 19:49 ` Nina Schoetterl-Glausch
2023-05-09 8:40 ` Pierre Morel
2023-04-25 16:14 ` [PATCH v20 11/21] qapi/s390x/cpu topology: CPU_POLARIZATION_CHANGE qapi event Pierre Morel
2023-05-08 21:47 ` Nina Schoetterl-Glausch
2023-05-09 12:31 ` Pierre Morel
2023-04-25 16:14 ` [PATCH v20 12/21] qapi/s390x/cpu topology: query-cpu-polarization qmp command Pierre Morel
2023-05-10 12:04 ` Nina Schoetterl-Glausch
2023-05-12 11:56 ` Pierre Morel
2023-04-25 16:14 ` [PATCH v20 13/21] docs/s390x/cpu topology: document s390x cpu topology Pierre Morel
2023-04-25 16:14 ` [PATCH v20 14/21] tests/avocado: s390x cpu topology core Pierre Morel
2023-05-22 19:38 ` Nina Schoetterl-Glausch
2023-06-27 11:58 ` Pierre Morel
2023-04-25 16:14 ` [PATCH v20 15/21] tests/avocado: s390x cpu topology polarisation Pierre Morel
2023-05-22 19:45 ` Nina Schoetterl-Glausch
2023-06-27 13:01 ` Pierre Morel
2023-04-25 16:14 ` [PATCH v20 16/21] tests/avocado: s390x cpu topology entitlement tests Pierre Morel
2023-05-22 19:47 ` Nina Schoetterl-Glausch
2023-06-27 13:22 ` Pierre Morel
2023-04-25 16:14 ` [PATCH v20 17/21] tests/avocado: s390x cpu topology test dedicated CPU Pierre Morel
2023-04-25 16:14 ` [PATCH v20 18/21] tests/avocado: s390x cpu topology test socket full Pierre Morel
2023-04-25 16:14 ` [PATCH v20 19/21] tests/avocado: s390x cpu topology dedicated errors Pierre Morel
2023-04-25 16:14 ` [PATCH v20 20/21] tests/avocado: s390x cpu topology bad move Pierre Morel
2023-04-25 16:14 ` [PATCH v20 21/21] tests/avocado: s390x cpu topology query-cpu-polarization 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=9ffdbd31-061c-619d-8902-69782ceed7a9@linux.ibm.com \
--to=pmorel@linux.ibm.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=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=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=seiden@linux.ibm.com \
--cc=thuth@redhat.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).