Re: [libvirt] [PATCH] rpc: allow truncated return for virDomainGetCPUStats

2012-03-07 Thread Eric Blake
On 03/07/2012 12:18 AM, Osier Yang wrote: On 03/07/2012 02:46 PM, Osier Yang wrote: On 03/07/2012 12:48 PM, Eric Blake wrote: The RPC code assumed that the array returned by the driver would be fully populated; that is, ncpus on entry resulted in ncpus * return value on exit. However, while

[libvirt] [PATCH] rpc: allow truncated return for virDomainGetCPUStats

2012-03-06 Thread Eric Blake
The RPC code assumed that the array returned by the driver would be fully populated; that is, ncpus on entry resulted in ncpus * return value on exit. However, while we don't support holes in the middle of ncpus, we do want to permit the case of ncpus on entry being longer than the array returned

Re: [libvirt] [PATCH] rpc: allow truncated return for virDomainGetCPUStats

2012-03-06 Thread Osier Yang
On 03/07/2012 12:48 PM, Eric Blake wrote: The RPC code assumed that the array returned by the driver would be fully populated; that is, ncpus on entry resulted in ncpus * return value on exit. However, while we don't support holes in the middle of ncpus, we do want to permit the case of ncpus

Re: [libvirt] [PATCH] rpc: allow truncated return for virDomainGetCPUStats

2012-03-06 Thread Osier Yang
On 03/07/2012 02:46 PM, Osier Yang wrote: On 03/07/2012 12:48 PM, Eric Blake wrote: The RPC code assumed that the array returned by the driver would be fully populated; that is, ncpus on entry resulted in ncpus * return value on exit. However, while we don't support holes in the middle of