qmp: expose s390-specific CPU info
commit9d0306dfdfb7e7fd8d5fbe45973566d1a8ea592d
authorViktor Mihajlovski <mihajlov@linux.vnet.ibm.com>
Fri, 16 Feb 2018 16:08:37 +0000 (16 17:08 +0100)
committerCornelia Huck <cohuck@redhat.com>
Mon, 26 Feb 2018 11:55:26 +0000 (26 12:55 +0100)
tree98e02b94f99b99997fb0d3b2d493c3f5f27ddb6f
parent21fc97c5fff10433d839047da44eee652f050041
qmp: expose s390-specific CPU info

Presently s390x is the only architecture not exposing specific
CPU information via QMP query-cpus. Upstream discussion has shown
that it could make sense to report the architecture specific CPU
state, e.g. to detect that a CPU has been stopped.

With this change the output of query-cpus will look like this on
s390:

   [
     {"arch": "s390", "current": true,
      "props": {"core-id": 0}, "cpu-state": "operating", "CPU": 0,
      "qom_path": "/machine/unattached/device[0]",
      "halted": false, "thread_id": 63115},
     {"arch": "s390", "current": false,
      "props": {"core-id": 1}, "cpu-state": "stopped", "CPU": 1,
      "qom_path": "/machine/unattached/device[1]",
      "halted": true, "thread_id": 63116}
   ]

This change doesn't add the s390-specific data to HMP 'info cpus'.
A follow-on patch will remove all architecture specific information
from there.

Signed-off-by: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Message-Id: <1518797321-28356-2-git-send-email-mihajlov@linux.vnet.ibm.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
cpus.c
hw/intc/s390_flic.c
hw/s390x/s390-virtio-ccw.c
qapi-schema.json
target/s390x/cpu.c
target/s390x/cpu.h
target/s390x/kvm.c
target/s390x/sigp.c