On 13/06/2016 10:42, Greg Kurz wrote:
> On Fri, 27 May 2016 13:16:49 +0200
> Greg Kurz wrote:
>
>> On Fri, 27 May 2016 13:58:28 +1000
>> David Gibson wrote:
>>
>>> On Thu, May 26, 2016 at 10:02:23AM +0200, Greg Kurz wrote:
As stated in linux/Documentation/virtual/kvm/api.txt:
On Fri, 27 May 2016 13:16:49 +0200
Greg Kurz wrote:
> On Fri, 27 May 2016 13:58:28 +1000
> David Gibson wrote:
>
> > On Thu, May 26, 2016 at 10:02:23AM +0200, Greg Kurz wrote:
> > > As stated in linux/Documentation/virtual/kvm/api.txt:
> > >
> > > The maximum possible value for max_vcpu_id c
On Fri, 27 May 2016 13:16:49 +0200
Greg Kurz wrote:
> On Fri, 27 May 2016 13:58:28 +1000
> David Gibson wrote:
>
> > On Thu, May 26, 2016 at 10:02:23AM +0200, Greg Kurz wrote:
> > > As stated in linux/Documentation/virtual/kvm/api.txt:
> > >
> > > The maximum possible value for max_vcpu_id c
On Fri, 27 May 2016 13:58:28 +1000
David Gibson wrote:
> On Thu, May 26, 2016 at 10:02:23AM +0200, Greg Kurz wrote:
> > As stated in linux/Documentation/virtual/kvm/api.txt:
> >
> > The maximum possible value for max_vcpu_id can be retrieved using the
> > KVM_CAP_MAX_VCPU_ID of the KVM_CHECK_EXT
On Thu, May 26, 2016 at 10:02:23AM +0200, Greg Kurz wrote:
> As stated in linux/Documentation/virtual/kvm/api.txt:
>
> The maximum possible value for max_vcpu_id can be retrieved using the
> KVM_CAP_MAX_VCPU_ID of the KVM_CHECK_EXTENSION ioctl() at run-time.
>
> If the KVM_CAP_MAX_VCPU_ID does no
As stated in linux/Documentation/virtual/kvm/api.txt:
The maximum possible value for max_vcpu_id can be retrieved using the
KVM_CAP_MAX_VCPU_ID of the KVM_CHECK_EXTENSION ioctl() at run-time.
If the KVM_CAP_MAX_VCPU_ID does not exist, you should assume that
max_vcpu_id is the same as the value re