On 12.02.2018 16:52, Cornelia Huck wrote:
> On Mon, 12 Feb 2018 13:14:30 +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}
>> ]
>>
>> Signed-off-by: Viktor Mihajlovski <mihaj...@linux.vnet.ibm.com>
>> Acked-by: Eric Blake <ebl...@redhat.com>
>> ---
>> cpus.c | 6 ++++++
>> hmp.c | 4 ++++
>> 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 +++++++++++++++++++-------------------
>> 9 files changed, 77 insertions(+), 44 deletions(-)
>
> Patch looks good to me. I presume this should go through the s390 tree?
> Or do we want someone to pick up the whole series?
>
The main reason for adding this patch to the series is to ensure
everything is applied in proper order. This patch can stand for itself,
but it must be applied before 3/3.
Valid orders would be 1 - 2 - 3 or 2 - 1 - 3.
As long as this is observed, I'm fine with either way.
--
Regards,
Viktor Mihajlovski
