On Tue, May 12, 2015 at 07:42:17PM +0200, Markus Armbruster wrote:
> Eduardo Habkost writes:
> > On Tue, May 12, 2015 at 05:38:37PM +0200, Markus Armbruster wrote:
> > [...]
> >> > @@ -699,8 +701,9 @@
> >> > #data is sent to the client, the guest may no longer be halted.
> >> > ##
> >> >
Eduardo Habkost writes:
> On Tue, May 12, 2015 at 05:38:37PM +0200, Markus Armbruster wrote:
> [...]
>> > @@ -699,8 +701,9 @@
>> > #data is sent to the client, the guest may no longer be halted.
>> > ##
>> > { 'struct': 'CpuInfo',
>> > - 'data': {'CPU': 'int', 'current': 'bool', 'halt
On Tue, May 12, 2015 at 05:38:37PM +0200, Markus Armbruster wrote:
[...]
> > @@ -699,8 +701,9 @@
> > #data is sent to the client, the guest may no longer be halted.
> > ##
> > { 'struct': 'CpuInfo',
> > - 'data': {'CPU': 'int', 'current': 'bool', 'halted': 'bool', '*pc': 'int',
> > -
Eduardo Habkost writes:
> This will allow clients to query additional information directly using
> qom-get on the CPU objects.
>
> Reviewed-by: David Gibson
> Reviewed-by: Andreas Färber
> Signed-off-by: Eduardo Habkost
> ---
> Changes v1 -> v2:
> * Renamed field from "qom-path" to "qom_path",
On 05/08/2015 01:04 PM, Eduardo Habkost wrote:
> This will allow clients to query additional information directly using
> qom-get on the CPU objects.
>
> Reviewed-by: David Gibson
> Reviewed-by: Andreas Färber
> Signed-off-by: Eduardo Habkost
> ---
> Changes v1 -> v2:
> * Renamed field from "qo
This will allow clients to query additional information directly using
qom-get on the CPU objects.
Reviewed-by: David Gibson
Reviewed-by: Andreas Färber
Signed-off-by: Eduardo Habkost
---
Changes v1 -> v2:
* Renamed field from "qom-path" to "qom_path", to keep consistency
with existing CpuInf
