From: Luiz Capitulino <lcapitulino@redhat.com>
To: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
Eric Blake <eblake@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] S390: Expose s390-specific CPU info
Date: Thu, 8 Feb 2018 11:22:16 -0500 [thread overview]
Message-ID: <20180208112216.0c4b6f3c@redhat.com> (raw)
In-Reply-To: <2b9e79d9-9c13-3edc-38f4-80062824e0b6@linux.vnet.ibm.com>
On Thu, 8 Feb 2018 16:52:28 +0100
Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com> wrote:
> diff --git a/qapi-schema.json b/qapi-schema.json
> index 12c7dc8..0b36860 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -607,7 +607,27 @@
> ##
> { 'struct': 'CpuInfo2',
> 'data': {'cpu-index': 'int', '*halted': 'bool', 'qom-path': 'str',
> - 'thread-id': 'int', '*props': 'CpuInstanceProperties' } }
> + 'thread-id': 'int', '*props': 'CpuInstanceProperties',
> + '*archdata': 'CpuInfoArchData' } }
> +
> +##
> +# @CpuInfoArchData:
> +#
> +# Architecure specific information about a virtual CPU
> +#
> +# Since: 2.12
> +#
> +##
> +{ 'union': 'CpuInfoArchData',
> + 'base': { 'arch': 'CpuInfoArch' },
> + 'discriminator': 'arch',
> + 'data': { 'x86': 'CpuInfoOther',
> + 'sparc': 'CpuInfoOther',
> + 'ppc': 'CpuInfoOther',
> + 'mips': 'CpuInfoOther',
> + 'tricore': 'CpuInfoOther',
> + 's390': 'CpuInfoS390',
> + 'other': 'CpuInfoOther' } }
>
> ##
> # @query-cpus-fast:
I don't think you need CpuInfoArchData, you can have S390CpuState
instead and ignore the other archs. It's not like all archs data
can be returned at the same time, and also you start having to
replicate that arch string list everywhere. Lastly, the arch name
is returned by query-target, so no need to duplicate that one either.
next prev parent reply other threads:[~2018-02-08 16:43 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 [this message]
2018-02-08 17:02 ` Viktor Mihajlovski
2018-02-08 17:37 ` Luiz Capitulino
2018-02-08 15:19 ` Eric Blake
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=20180208112216.0c4b6f3c@redhat.com \
--to=lcapitulino@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=eblake@redhat.com \
--cc=mihajlov@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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).