aboutsummaryrefslogtreecommitdiff
path: root/qapi-schema.json
diff options
context:
space:
mode:
authorDavid Hildenbrand <david@redhat.com>2017-10-20 13:58:03 +0200
committerChristian Borntraeger <borntraeger@de.ibm.com>2017-10-30 08:56:28 +0100
commite555cbe78d59f09f7e7db7703d1e91b95f2743c0 (patch)
tree913bbb77713188c89ee5d20ec4b214f862c8f49e /qapi-schema.json
parenta93ece47fd9edbd4558db24300056c9a57d3bcd4 (diff)
downloadqemu-e555cbe78d59f09f7e7db7703d1e91b95f2743c0.zip
qemu-e555cbe78d59f09f7e7db7703d1e91b95f2743c0.tar.gz
qemu-e555cbe78d59f09f7e7db7703d1e91b95f2743c0.tar.bz2
target/s390x: change CPU type name to "s390x-cpu"
For now, e.g. host-s390-cpu wasn't exposed to the user. cpu-add, -cpu and the CPU model qmp interfaces didn't care about the actual type, as that information was hidden. This changed with CPU hotplug via device_add. Now the type is visible to the user. Before we get that supported in a stable version, this is our last chance to change it. So change it from "s390-cpu" to "s390x-cpu", to match the architecture name. Example names are then e.g. z14-s390x-cpu or qemu-s390x-cpu. Signed-off-by: David Hildenbrand <david@redhat.com> Message-Id: <20171020115803.14093-1-david@redhat.com> Acked-by: Cornelia Huck <cohuck@redhat.com> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Diffstat (limited to 'qapi-schema.json')
-rw-r--r--qapi-schema.json4
1 files changed, 2 insertions, 2 deletions
diff --git a/qapi-schema.json b/qapi-schema.json
index a9dd043..1845795 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -3159,12 +3159,12 @@
# -> { "execute": "query-hotpluggable-cpus" }
# <- {"return": [
# {
-# "type": "qemu-s390-cpu", "vcpus-count": 1,
+# "type": "qemu-s390x-cpu", "vcpus-count": 1,
# "props": { "core-id": 1 }
# },
# {
# "qom-path": "/machine/unattached/device[0]",
-# "type": "qemu-s390-cpu", "vcpus-count": 1,
+# "type": "qemu-s390x-cpu", "vcpus-count": 1,
# "props": { "core-id": 0 }
# }
# ]}