On Fri, 16 Feb 2018 17:08:37 +0100
Viktor Mihajlovski <mihaj...@linux.vnet.ibm.com> wrote:

> 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 <mihaj...@linux.vnet.ibm.com>
> Reviewed-by: David Hildenbrand <da...@redhat.com>
> Reviewed-by: Christian Borntraeger <borntrae...@de.ibm.com>
> Reviewed-by: Eric Blake <ebl...@redhat.com>
> ---
>  cpus.c                     |  6 ++++++
>  hw/intc/s390_flic.c        |  4 ++--
>  hw/s390x/s390-virtio-ccw.c |  2 +-
>  qapi-schema.json           | 28 +++++++++++++++++++++++++++-
>  target/s390x/cpu.c         | 24 ++++++++++++------------
>  target/s390x/cpu.h         |  7 ++-----
>  target/s390x/kvm.c         |  8 ++++----
>  target/s390x/sigp.c        | 38 +++++++++++++++++++-------------------
>  8 files changed, 73 insertions(+), 44 deletions(-)

Reviewed-by: Cornelia Huck <coh...@redhat.com>

Reply via email to