From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45662)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jdenemar@redhat.com>) id 1b0kua-0003RD-Av
	for qemu-devel@nongnu.org; Thu, 12 May 2016 03:19:57 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jdenemar@redhat.com>) id 1b0kuW-0004XW-2P
	for qemu-devel@nongnu.org; Thu, 12 May 2016 03:19:55 -0400
Received: from mx1.redhat.com ([209.132.183.28]:41669)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jdenemar@redhat.com>) id 1b0kuV-0004XI-St
	for qemu-devel@nongnu.org; Thu, 12 May 2016 03:19:52 -0400
Date: Thu, 12 May 2016 09:19:48 +0200
From: Jiri Denemark <jdenemar@redhat.com>
Message-ID: <20160512071948.GC3675719@orkuz.home>
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>
	<877ff2fhjf.fsf@dusky.pond.sub.org>
	<20160510115705.GX4457@thinpad.lan.raisama.net>
	<87bn4djcgq.fsf@dusky.pond.sub.org>
	<20160511193550.GD24153@thinpad.lan.raisama.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160511193550.GD24153@thinpad.lan.raisama.net>
Subject: Re: [Qemu-devel] [libvirt] [PATCH 7/9] qmp: Add runnability
 information to query-cpu-definitions
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>, Christian Borntraeger <borntraeger@de.ibm.com>, libvir-list@redhat.com, qemu-devel@nongnu.org, David Hildenbrand <dahi@linux.vnet.ibm.com>, Cornelia Huck <cornelia.huck@de.ibm.com>, Igor Mammedov <imammedo@redhat.com>, Andreas =?iso-8859-1?Q?F=E4rber?= <afaerber@suse.de>

On Wed, May 11, 2016 at 16:35:50 -0300, Eduardo Habkost wrote:
> # @CpuDefinitionInfo:
> #
> # Virtual CPU definition.
> #
> # @name: the name of the CPU definition
> # @runnable: #optional. whether the CPU model us usable with the

s/ us / is /

> #            current machine and accelerator. Omitted if we don't
> #            know the answer. (since 2.7)
> # @unavailable-features: List of attributes that prevent the CPU
> #                        model from running in the current host.
> #                        (since 2.7)
> #
> # @unavailable-features is a list of QOM property names that
> # represent CPU model attributes that prevent the CPU from running.
> # If the QOM property is read-only, that means the CPU model can
> # never run in the current host. If the property is read-write, it
> # means that it MAY be possible to run the CPU model in the current
> # host if that property is changed. Management software can use it
> # as hints to suggest or choose an alternative for the user, or
> # just to generate meaningful error messages explaining why the CPU
> # model can't be used.

Any chance this could be extended to provide data about every single
machine type rather than just the current one?

Jirka