From: Cornelia Huck <cohuck@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, agraf@suse.de, ehabkost@redhat.com,
armbru@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] [PATCHv2 3/3] qmp: add architecture specific cpu data for query-cpus-fast
Date: Wed, 14 Feb 2018 16:27:15 +0100 [thread overview]
Message-ID: <20180214162715.54743e55.cohuck@redhat.com> (raw)
In-Reply-To: <a0d9f591-8f6d-4c98-8b71-cb8585c1ef12@redhat.com>
On Wed, 14 Feb 2018 09:15:23 -0600
Eric Blake <eblake@redhat.com> wrote:
> On 02/14/2018 04:15 AM, Cornelia Huck wrote:
> > On Tue, 13 Feb 2018 18:18:48 +0100
> > Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com> wrote:
> >
>
> >> A suggestion was made on the mailing list to enhance the QAPI
> >> code generation to support two layers of unions. This would
> >> allow to specify the common fields once and avoid the duplication
> >> in the leaf unions.
> >>
> >> On the other hand, the slow query-cpus should be deprecated
> >> along with the slow CpuInfo type and eventually be removed.
> >> Assuming that new architectures will not be added at high
> >> rates, we could live with the duplication for the time being.
> >
> > What would be a realistic timeframe for deprecation/removal of
> > query-cpus, considering the libvirt usage? Are we aware of other users?
>
> Well, if we want to start the clock ticking, this series also needs to
> touch qemu-doc.texi to start the deprecation clock, then we go at least
> two more releases with support for both old and new commands.
>
I'd like to know first what libvirt plans to do -- no sense in starting
deprecation if we're still stuck with it for a while.
next prev parent reply other threads:[~2018-02-14 15:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 17:18 [Qemu-devel] [PATCHv2 0/3] add query-cpu-fast and related s390 changes Viktor Mihajlovski
2018-02-13 17:18 ` [Qemu-devel] [PATCHv2 1/3] qmp: expose s390-specific CPU info Viktor Mihajlovski
2018-02-14 9:30 ` Christian Borntraeger
2018-02-14 9:46 ` David Hildenbrand
2018-02-13 17:18 ` [Qemu-devel] [PATCHv2 2/3] qmp: add query-cpus-fast Viktor Mihajlovski
2018-02-14 10:11 ` Cornelia Huck
2018-02-14 19:46 ` Eric Blake
2018-02-13 17:18 ` [Qemu-devel] [PATCHv2 3/3] qmp: add architecture specific cpu data for query-cpus-fast Viktor Mihajlovski
2018-02-14 10:15 ` Cornelia Huck
2018-02-14 15:15 ` Eric Blake
2018-02-14 15:27 ` Cornelia Huck [this message]
2018-02-14 15:50 ` Viktor Mihajlovski
2018-02-14 16:07 ` Eric Blake
2018-02-14 19:56 ` Eric Blake
2018-02-14 10:57 ` [Qemu-devel] [PATCHv2 0/3] add query-cpu-fast and related s390 changes Cornelia Huck
2018-02-14 14:00 ` Viktor Mihajlovski
2018-02-14 15:49 ` Dr. David Alan Gilbert
2018-02-14 15:16 ` Eric Blake
2018-02-14 15:26 ` Cornelia Huck
2018-02-14 20:01 ` 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=20180214162715.54743e55.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@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).