[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [libvirt] [Qemu-devel] [PATCH 7/9] qmp: Add runnability information to query-cpu-definitions
- From: David Hildenbrand <dahi linux vnet ibm com>
- To: Eduardo Habkost <ehabkost redhat com>
- Cc: Andreas, libvir-list redhat com, qemu-devel nongnu org, Christian Borntraeger <borntraeger de ibm com>, Cornelia Huck <cornelia huck de ibm com>, Igor Mammedov <imammedo redhat com>, Jiri Denemark <jdenemar redhat com>, Färber <afaerber suse de>
- Subject: Re: [libvirt] [Qemu-devel] [PATCH 7/9] qmp: Add runnability information to query-cpu-definitions
- Date: Thu, 12 May 2016 08:46:34 +0200
> Updated to:
>
> ##
> # @CpuDefinitionInfo:
> #
> # Virtual CPU definition.
> #
> # @name: the name of the CPU definition
> # @runnable: #optional. whether the CPU model us usable with the
> # current machine and accelerator. Omitted if we don't
> # know the answer. (since 2.7)
> # @unavailable-features: List of attributes that prevent the CPU
"List of properties" ?
> # 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.
> #
> # Since: 1.2.0
> ##
>
what about changing unavailable-features to
problematic-properties
responsible-properties
... anything else making clear that we are dealing with properties, not
only features?
Apart from that, sounds good to me.
David
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]