qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	libvir-list@redhat.com, dahi@linux.vnet.ibm.com,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	Igor Mammedov <imammedo@redhat.com>,
	Jiri Denemark <jdenemar@redhat.com>
Subject: Re: [Qemu-devel] [libvirt] [PATCH v3 4/5] qmp: Add runnability information to query-cpu-definitions
Date: Tue, 20 Sep 2016 13:25:06 -0500	[thread overview]
Message-ID: <be884b2f-eb07-2f90-4f7a-8dc921a6de52@redhat.com> (raw)
In-Reply-To: <1474314175-24374-5-git-send-email-ehabkost@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]

On 09/19/2016 02:42 PM, Eduardo Habkost wrote:
> Add a new optional field to query-cpu-definitions schema:
> "unavailable-features". It will contain a list of QOM properties
> that prevent the CPU model from running in the current host.
> 
> Cc: David Hildenbrand <dahi@linux.vnet.ibm.com>
> Cc: Michael Mueller <mimu@linux.vnet.ibm.com>
> Cc: Christian Borntraeger <borntraeger@de.ibm.com>
> Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
> Cc: Jiri Denemark <jdenemar@redhat.com>
> Cc: libvir-list@redhat.com
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> ---

> +++ b/qapi-schema.json
> @@ -3111,10 +3111,31 @@
>  #          QEMU version, machine type, machine options and accelerator options.
>  #          A static model is always migration-safe. (since 2.8)
>  #
> +# @unavailable-features: #optional List of properties that prevent
> +#                        the CPU model from running in the current
> +#                        host. (since 2.7)

We've missed 2.7; this should probably be 2.8.  Otherwise reads okay to me;

Reviewed-by: Eric Blake <eblake@redhat.com>

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2016-09-20 18:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19 19:42 [Qemu-devel] [PATCH v3 0/5] Add runnability info to query-cpu-definitions Eduardo Habkost
2016-09-19 19:42 ` [Qemu-devel] [PATCH v3 1/5] target-i386: List CPU models using subclass list Eduardo Habkost
2016-09-19 19:42 ` [Qemu-devel] [PATCH v3 2/5] target-i386: Move warning code outside x86_cpu_filter_features() Eduardo Habkost
2016-09-19 19:42 ` [Qemu-devel] [PATCH v3 3/5] target-i386: Define CPUID filtering functions before x86_cpu_list() Eduardo Habkost
2016-09-19 19:42 ` [Qemu-devel] [PATCH v3 4/5] qmp: Add runnability information to query-cpu-definitions Eduardo Habkost
2016-09-20 18:25   ` Eric Blake [this message]
2016-09-20 19:05     ` [Qemu-devel] [libvirt] " Eduardo Habkost
2016-09-19 19:42 ` [Qemu-devel] [PATCH v3 5/5] target-i386: Return runnability information on query-cpu-definitions Eduardo Habkost
2016-09-19 21:16 ` [Qemu-devel] [libvirt] [PATCH v3 0/5] Add runnability info to query-cpu-definitions no-reply

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=be884b2f-eb07-2f90-4f7a-8dc921a6de52@redhat.com \
    --to=eblake@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=dahi@linux.vnet.ibm.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=jdenemar@redhat.com \
    --cc=libvir-list@redhat.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).