On Tue, Aug 23, 2016 at 17:54:51 +0530, Shivaprasad G Bhat wrote:
> On 08/19/2016 08:08 PM, Peter Krempa wrote:
[...]
> > +/* match entries from query cpus to the output array taking into
> > account
> > + * multi-vcpu objects */
> > +for (j = 0; j < ncpuentries; j++) {
> > +
On 08/19/2016 08:08 PM, Peter Krempa wrote:
For hotplug purposes it's necessary to retrieve data using
query-hotpluggable-cpus while the old query-cpus API report thread IDs
and order of hotplug.
This patch adds code that merges the data using a rather non-trivial
algorithm and fills the data
On 08/19/2016 02:33 PM, John Ferlan wrote:
>
>
[...]
>> +/**
>> + * qemuMonitorGetCPUInfoHotplug:
>> + *
>> + * This function stitches together data retrieved via
>> query-hotpluggable-cpus
>> + * which returns entities on the hotpluggable level (which may describe more
>> + * than one guest
On 08/19/2016 10:38 AM, Peter Krempa wrote:
> For hotplug purposes it's necessary to retrieve data using
> query-hotpluggable-cpus while the old query-cpus API report thread IDs
> and order of hotplug.
>
> This patch adds code that merges the data using a rather non-trivial
> algorithm and fills
For hotplug purposes it's necessary to retrieve data using
query-hotpluggable-cpus while the old query-cpus API report thread IDs
and order of hotplug.
This patch adds code that merges the data using a rather non-trivial
algorithm and fills the data to the qemuMonitorCPUInfo structure for
adding t