From: Eric Blake <eblake@redhat.com>
To: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: agraf@suse.de, ehabkost@redhat.com, armbru@redhat.com,
cohuck@redhat.com, david@redhat.com, dgilbert@redhat.com,
borntraeger@de.ibm.com, qemu-s390x@nongnu.org,
pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCHv4 1/4] qmp: expose s390-specific CPU info
Date: Fri, 16 Feb 2018 07:55:13 -0600 [thread overview]
Message-ID: <87e8b127-7f91-3f9a-7d2e-9195ef6cb48d@redhat.com> (raw)
In-Reply-To: <1518782691-1232-2-git-send-email-mihajlov@linux.vnet.ibm.com>
On 02/16/2018 06:04 AM, Viktor Mihajlovski 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}
> ]
Maybe worth adding the comment that:
HMP "info cpus" is intentionally not modified, as a later patch will be
pruning it down anyways.
>
> Signed-off-by: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>
> Acked-by: Eric Blake <eblake@redhat.com>
> Reviewed-by: David Hildenbrand <david@redhat.com>
> Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.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(-)
>
I've now read closely through the entire patch; you can upgrade my
Acked-by into
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-02-16 13:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 12:04 [Qemu-devel] [PATCHv4 0/4] add query-cpu-fast and related s390 changes Viktor Mihajlovski
2018-02-16 12:04 ` [Qemu-devel] [PATCHv4 1/4] qmp: expose s390-specific CPU info Viktor Mihajlovski
2018-02-16 13:55 ` Eric Blake [this message]
2018-02-16 12:04 ` [Qemu-devel] [PATCHv4 2/4] qmp: add query-cpus-fast Viktor Mihajlovski
2018-02-16 14:03 ` Eric Blake
2018-02-16 14:49 ` Viktor Mihajlovski
2018-02-16 15:07 ` Eric Blake
2018-02-16 15:38 ` Dr. David Alan Gilbert
2018-02-16 12:04 ` [Qemu-devel] [PATCHv4 3/4] qmp: add architecture specific cpu data for query-cpus-fast Viktor Mihajlovski
2018-02-16 14:05 ` Eric Blake
2018-02-16 12:04 ` [Qemu-devel] [PATCHv4 4/4] qemu-doc: deprecate query-cpus Viktor Mihajlovski
2018-02-16 14:05 ` Eric Blake
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=87e8b127-7f91-3f9a-7d2e-9195ef6cb48d@redhat.com \
--to=eblake@redhat.com \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mihajlov@linux.vnet.ibm.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).