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 0/3] add query-cpu-fast and related s390 changes
Date: Wed, 14 Feb 2018 16:26:12 +0100 [thread overview]
Message-ID: <20180214162612.70506465.cohuck@redhat.com> (raw)
In-Reply-To: <a6135d66-6673-a49d-01fa-9fa4d55b3aa1@redhat.com>
On Wed, 14 Feb 2018 09:16:15 -0600
Eric Blake <eblake@redhat.com> wrote:
> On 02/14/2018 04:57 AM, Cornelia Huck wrote:
> > On Tue, 13 Feb 2018 18:18:45 +0100
> > Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com> wrote:
> >
>
> >> Patch 1/3:
> >> Adds architecture specific data to the QMP CpuInfo type, exposing
> >> the existing s390 cpu-state in QMP. The cpu-state is a representation
> >> more adequate than the ambiguous 'halted' condition.
> >>
> >> Patch 2/3:
> >> Adds a new QMP function query-cpus-fast, which will only retrieve
> >> vCPU information that can be obtained without interrupting the
> >> vCPUs of a running VM. It introduces a new return type CpuInfoFast
> >> with the subset of fields meeting this condition. Specifically, the
> >> halted state is not part of CpuInfoFast. QMP clients like libvirt
> >> are encouraged to switch to the new API for vCPU information.
> >>
> >> Patch 3/3:
> >> Adds the s390-specific cpu state to CpuInfoFast, allowing management
> >> apps to find out whether a vCPU is in the stopped state. This extension
> >> leads to a partial duplication of field definitions from CpuInfo
> >> to CpuInfoFast. This should be tolerable if CpuInfo is deprecated and
> >> eventually removed.
> >
> > How shall we proceed with this series? Patch 3 depends upon patch 1, so
> > I think it makes sense to merge this in one go.
> >
> > I can give my R-b on patch 1 and Someone(tm) can merge this, or I can
> > take the whole series through the s390 tree (with some further
> > reviews/acks on patches 2/3).
>
> I'd still like to give a thorough QMP review; it's on my list to get to
> today.
>
Sure, no need to hurry.
next prev parent reply other threads:[~2018-02-14 15:52 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
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 [this message]
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=20180214162612.70506465.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.