From: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
lcapitulino@redhat.com, ehabkost@redhat.com, pbonzini@redhat.com,
crosthwaite.peter@gmail.com, dgilbert@redhat.com,
rth@twiddle.net, borntraeger@de.ibm.com, agraf@suse.de,
david@redhat.com, eblake@redhat.com, armbru@redhat.com,
berrange@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/3] qmp: expose s390-specific CPU info
Date: Mon, 12 Feb 2018 17:20:20 +0100 [thread overview]
Message-ID: <f1fa0d61-bda9-e6e2-0b71-aa851a87f855@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180212165228.2021b4d4.cohuck@redhat.com>
On 12.02.2018 16:52, Cornelia Huck wrote:
> On Mon, 12 Feb 2018 13:14:30 +0100
> Viktor Mihajlovski <mihajlov@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 <mihajlov@linux.vnet.ibm.com>
>> Acked-by: Eric Blake <eblake@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
next prev parent reply other threads:[~2018-02-12 16:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 12:14 [Qemu-devel] [PATCH 0/3] add query-cpu-fast and related s390 changes Viktor Mihajlovski
2018-02-12 12:14 ` [Qemu-devel] [PATCH 1/3] qmp: expose s390-specific CPU info Viktor Mihajlovski
2018-02-12 15:52 ` Cornelia Huck
2018-02-12 16:20 ` Viktor Mihajlovski [this message]
2018-02-12 18:03 ` Luiz Capitulino
2018-02-13 11:16 ` [Qemu-devel] [qemu-s390x] " David Hildenbrand
2018-02-13 12:20 ` Viktor Mihajlovski
2018-02-13 15:10 ` Eric Blake
2018-02-12 20:30 ` [Qemu-devel] " David Hildenbrand
2018-02-12 12:14 ` [Qemu-devel] [PATCH 2/3] qmp: add query-cpus-fast Viktor Mihajlovski
2018-02-12 16:06 ` Cornelia Huck
2018-02-12 16:50 ` Dr. David Alan Gilbert
2018-02-13 15:14 ` Viktor Mihajlovski
2018-02-12 20:35 ` David Hildenbrand
2018-02-12 12:14 ` [Qemu-devel] [PATCH 3/3] qmp: add architecture specific cpu data for query-cpus-fast Viktor Mihajlovski
2018-02-12 16:23 ` Cornelia Huck
2018-02-13 16:12 ` Viktor Mihajlovski
2018-02-13 16:17 ` Cornelia Huck
2018-02-12 18:15 ` Luiz Capitulino
2018-02-13 12:30 ` Viktor Mihajlovski
2018-02-13 13:41 ` Luiz Capitulino
2018-02-12 15:38 ` [Qemu-devel] [PATCH 0/3] add query-cpu-fast and related s390 changes Cornelia Huck
2018-02-12 16:26 ` Viktor Mihajlovski
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=f1fa0d61-bda9-e6e2-0b71-aa851a87f855@linux.vnet.ibm.com \
--to=mihajlov@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=crosthwaite.peter@gmail.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
/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).