From: Pierre Morel <pmorel@linux.ibm.com>
To: qemu-s390x@nongnu.org
Cc: qemu-devel@nongnu.org, borntraeger@de.ibm.com,
pasic@linux.ibm.com, richard.henderson@linaro.org,
david@redhat.com, thuth@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: [PATCH v18 11/17] qapi/s390x/cpu topology: CPU_POLARIZATION_CHANGE qapi event
Date: Wed, 15 Mar 2023 15:34:56 +0100 [thread overview]
Message-ID: <20230315143502.135750-12-pmorel@linux.ibm.com> (raw)
In-Reply-To: <20230315143502.135750-1-pmorel@linux.ibm.com>
When the guest asks to change the polarization this change
is forwarded to the upper layer using QAPI.
The upper layer is supposed to take according decisions concerning
CPU provisioning.
Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
---
qapi/machine-target.json | 33 +++++++++++++++++++++++++++++++++
hw/s390x/cpu-topology.c | 2 ++
2 files changed, 35 insertions(+)
diff --git a/qapi/machine-target.json b/qapi/machine-target.json
index 3b7a0b77f4..ffde2e9cbd 100644
--- a/qapi/machine-target.json
+++ b/qapi/machine-target.json
@@ -391,3 +391,36 @@
'features': [ 'unstable' ],
'if': { 'all': [ 'TARGET_S390X' , 'CONFIG_KVM' ] }
}
+
+##
+# @CPU_POLARIZATION_CHANGE:
+#
+# Emitted when the guest asks to change the polarization.
+#
+# @polarization: polarization specified by the guest
+#
+# Features:
+# @unstable: This command may still be modified.
+#
+# The guest can tell the host (via the PTF instruction) whether the
+# CPUs should be provisioned using horizontal or vertical polarization.
+#
+# On horizontal polarization the host is expected to provision all vCPUs
+# equally.
+# On vertical polarization the host can provision each vCPU differently.
+# The guest will get information on the details of the provisioning
+# the next time it uses the STSI(15) instruction.
+#
+# Since: 8.1
+#
+# Example:
+#
+# <- { "event": "CPU_POLARIZATION_CHANGE",
+# "data": { "polarization": 0 },
+# "timestamp": { "seconds": 1401385907, "microseconds": 422329 } }
+##
+{ 'event': 'CPU_POLARIZATION_CHANGE',
+ 'data': { 'polarization': 'CpuS390Polarization' },
+ 'features': [ 'unstable' ],
+ 'if': { 'all': [ 'TARGET_S390X', 'CONFIG_KVM' ] }
+}
diff --git a/hw/s390x/cpu-topology.c b/hw/s390x/cpu-topology.c
index 1cf3adec31..39c6d262e3 100644
--- a/hw/s390x/cpu-topology.c
+++ b/hw/s390x/cpu-topology.c
@@ -19,6 +19,7 @@
#include "hw/s390x/s390-virtio-ccw.h"
#include "hw/s390x/cpu-topology.h"
#include "qapi/qapi-commands-machine-target.h"
+#include "qapi/qapi-events-machine-target.h"
/*
* s390_topology is used to keep the topology information.
@@ -160,6 +161,7 @@ void s390_handle_ptf(S390CPU *cpu, uint8_t r1, uintptr_t ra)
s390_topology.polarization = fc;
s390_topology_set_cpus_entitlement();
s390_cpu_topology_set_changed(true);
+ qapi_event_send_cpu_polarization_change(fc);
setcc(cpu, 0);
}
break;
--
2.31.1
next prev parent reply other threads:[~2023-03-15 14:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 14:34 [PATCH v18 00/17] s390x: CPU Topology Pierre Morel
2023-03-15 14:34 ` [PATCH v18 01/17] s390x/cpu topology: add s390 specifics to CPU topology Pierre Morel
2023-03-27 21:34 ` Nina Schoetterl-Glausch
2023-03-28 11:29 ` Pierre Morel
2023-03-15 14:34 ` [PATCH v18 02/17] s390x/cpu topology: add topology entries on CPU hotplug Pierre Morel
2023-03-15 14:34 ` [PATCH v18 03/17] target/s390x/cpu topology: handle STSI(15) and build the SYSIB Pierre Morel
2023-03-15 14:34 ` [PATCH v18 04/17] s390x/sclp: reporting the maximum nested topology entries Pierre Morel
2023-03-15 14:34 ` [PATCH v18 05/17] s390x/cpu topology: resetting the Topology-Change-Report Pierre Morel
2023-03-15 14:34 ` [PATCH v18 06/17] s390x/cpu topology: interception of PTF instruction Pierre Morel
2023-03-15 14:34 ` [PATCH v18 07/17] target/s390x/cpu topology: activate CPU topology Pierre Morel
2023-03-15 14:34 ` [PATCH v18 08/17] qapi/s390x/cpu topology: set-cpu-topology qmp command Pierre Morel
2023-03-15 14:34 ` [PATCH v18 09/17] machine: adding s390 topology to query-cpu-fast Pierre Morel
2023-03-15 14:34 ` [PATCH v18 10/17] machine: adding s390 topology to info hotpluggable-cpus Pierre Morel
2023-03-15 14:34 ` Pierre Morel [this message]
2023-03-15 14:34 ` [PATCH v18 12/17] docs/s390x/cpu topology: document s390x cpu topology Pierre Morel
2023-03-15 14:34 ` [PATCH v18 13/17] tests/avocado: s390x cpu topology core Pierre Morel
2023-03-15 14:34 ` [PATCH v18 14/17] tests/avocado: s390x cpu topology polarisation Pierre Morel
2023-03-15 14:35 ` [PATCH v18 15/17] tests/avocado: s390x cpu topology entitlement tests Pierre Morel
2023-03-15 14:35 ` [PATCH v18 16/17] tests/avocado: s390x cpu topology test dedicated CPU Pierre Morel
2023-03-15 14:35 ` [PATCH v18 17/17] tests/avocado: s390x cpu topology test socket full 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=20230315143502.135750-12-pmorel@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).