From: Eric Blake <eblake@redhat.com>
To: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] S390: Expose s390-specific CPU info
Date: Thu, 8 Feb 2018 09:19:41 -0600 [thread overview]
Message-ID: <3e34d51f-e4d1-a69b-1fac-c4d1982834c2@redhat.com> (raw)
In-Reply-To: <1518083288-20410-1-git-send-email-mihajlov@linux.vnet.ibm.com>
On 02/08/2018 03:48 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}]
>
> Signed-off-by: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>
> ---
> +++ b/qapi-schema.json
> @@ -413,7 +413,7 @@
> # Since: 2.6
> ##
> { 'enum': 'CpuInfoArch',
> - 'data': ['x86', 'sparc', 'ppc', 'mips', 'tricore', 'other' ] }
> + 'data': ['x86', 'sparc', 'ppc', 'mips', 'tricore', 's390', 'other' ] }
Missing a documentation line that mentions when the enum grew. Also, has
a conflict with this other proposed addition, which demonstrates what
the documentation should look like (should be easy to resolve, though):
https://lists.gnu.org/archive/html/qemu-devel/2018-02/msg01986.html
> ##
> +# @CpuInfoS390State:
> +#
> +# An enumeration of cpu states that can be assumed by a virtual
> +# S390 CPU
> +#
> +# Since: 2.12
> +##
> +{ 'enum': 'CpuInfoS390State',
> + 'data': [ 'uninitialized', 'stopped', 'check_stop', 'operating', 'load' ] }
> +
Is there a consistency reason for naming this 'check_stop', or can we go
with our preference for using dash 'check-stop'?
> +##
> +# @CpuInfoS390:
> +#
> +# Additional information about a virtual S390 CPU
> +#
> +# @cpu_state: the CPUs state
> +#
> +# Since: 2.12
> +##
> +{ 'struct': 'CpuInfoS390', 'data': { 'cpu_state': 'CpuInfoS390State' } }
Likewise for 'cpu-state'
--
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-08 15:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 9:48 [Qemu-devel] [PATCH] S390: Expose s390-specific CPU info Viktor Mihajlovski
2018-02-08 10:16 ` Cornelia Huck
2018-02-08 10:24 ` Christian Borntraeger
2018-02-08 10:37 ` Cornelia Huck
2018-02-08 15:25 ` Eric Blake
2018-02-08 14:09 ` Luiz Capitulino
2018-02-08 15:21 ` Cornelia Huck
2018-02-08 15:30 ` Luiz Capitulino
2018-02-08 15:52 ` Viktor Mihajlovski
2018-02-08 16:22 ` Luiz Capitulino
2018-02-08 17:02 ` Viktor Mihajlovski
2018-02-08 17:37 ` Luiz Capitulino
2018-02-08 15:19 ` Eric Blake [this message]
2018-02-08 15:30 ` 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=3e34d51f-e4d1-a69b-1fac-c4d1982834c2@redhat.com \
--to=eblake@redhat.com \
--cc=mihajlov@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
/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).