From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46305) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b02wv-000481-9Y for qemu-devel@nongnu.org; Tue, 10 May 2016 04:23:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b02wq-0000Ol-33 for qemu-devel@nongnu.org; Tue, 10 May 2016 04:23:25 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39135) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b02wp-0000Oc-Tf for qemu-devel@nongnu.org; Tue, 10 May 2016 04:23:20 -0400 From: Markus Armbruster References: <1462558292-2126-1-git-send-email-ehabkost@redhat.com> <1462558292-2126-8-git-send-email-ehabkost@redhat.com> <5730AAAF.7040205@redhat.com> <20160509192515.GU4457@thinpad.lan.raisama.net> Date: Tue, 10 May 2016 10:23:16 +0200 In-Reply-To: <20160509192515.GU4457@thinpad.lan.raisama.net> (Eduardo Habkost's message of "Mon, 9 May 2016 16:25:15 -0300") Message-ID: <877ff2fhjf.fsf@dusky.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Qemu-devel] [libvirt] [PATCH 7/9] qmp: Add runnability information to query-cpu-definitions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost Cc: Eric Blake , David Hildenbrand , libvir-list@redhat.com, qemu-devel@nongnu.org, Christian Borntraeger , Cornelia Huck , Igor Mammedov , Jiri Denemark , Andreas =?utf-8?Q?F=C3=A4rber?= Eduardo Habkost writes: > On Mon, May 09, 2016 at 09:20:15AM -0600, Eric Blake wrote: >> On 05/06/2016 12:11 PM, Eduardo Habkost wrote: >> > Extend query-cpu-definitions schema to allow it to return two new >> > optional fields: "runnable" and "unavailable-features". >> > "runnable" will tell if the CPU model can be run in the current >> > host. "unavailable-features" will contain a list of CPU >> > properties that are preventing the CPU model from running in the >> > current host. >> > >> > Cc: David Hildenbrand >> > Cc: Michael Mueller >> > Cc: Christian Borntraeger >> > Cc: Cornelia Huck >> > Cc: Jiri Denemark >> > Cc: libvir-list@redhat.com >> > Signed-off-by: Eduardo Habkost >> > --- >> > qapi-schema.json | 10 +++++++++- >> > 1 file changed, 9 insertions(+), 1 deletion(-) >> > >> > diff --git a/qapi-schema.json b/qapi-schema.json >> > index 54634c4..450e6e7 100644 >> > --- a/qapi-schema.json >> > +++ b/qapi-schema.json >> > @@ -2948,11 +2948,19 @@ >> > # Virtual CPU definition. >> > # >> > # @name: the name of the CPU definition >> > +# @runnable: true if the CPU model is runnable using the current >> > +# machine and accelerator. Optional. Since 2.6. >> >> You've missed 2.6. Also, the typical spelling for a per-member >> designation is '(since 2.7)', not 'Since 2.7' > > Oops! I meant 2.7, and I didn't notice that it was not using the > typical format. I will fix it, thanks. > >> >> Why is it optional? Would it hurt to always be present in qemu new >> enough to understand why it is needed? > > It is optional because not all architectures will return the > field. This series implements it only for x86. Its documentation seems to suggest missing runnable has the same meaning as runnable: false. Is that correct?