Re: [PATCH v5 2/2] kvm: introduce KVM_MAX_VCPU_ID

2016-05-04 Thread Greg Kurz
On Wed, 4 May 2016 18:45:34 +0200 Radim Krčmář wrote: > 2016-05-03 06:52+0200, Greg Kurz: > > The KVM_MAX_VCPUS define provides the maximum number of vCPUs per guest, and > > also the upper limit for vCPU ids. This is okay for all archs except PowerPC > > which can have

Re: [PATCH v5 2/2] kvm: introduce KVM_MAX_VCPU_ID

2016-05-04 Thread Greg Kurz
On Wed, 4 May 2016 18:45:34 +0200 Radim Krčmář wrote: > 2016-05-03 06:52+0200, Greg Kurz: > > The KVM_MAX_VCPUS define provides the maximum number of vCPUs per guest, and > > also the upper limit for vCPU ids. This is okay for all archs except PowerPC > > which can have higher ids, depending on

Re: [PATCH v5 2/2] kvm: introduce KVM_MAX_VCPU_ID

2016-05-04 Thread Radim Krčmář
2016-05-03 06:52+0200, Greg Kurz: > The KVM_MAX_VCPUS define provides the maximum number of vCPUs per guest, and > also the upper limit for vCPU ids. This is okay for all archs except PowerPC > which can have higher ids, depending on the cpu/core/thread topology. In the > worst case (single

Re: [PATCH v5 2/2] kvm: introduce KVM_MAX_VCPU_ID

2016-05-04 Thread Radim Krčmář
2016-05-03 06:52+0200, Greg Kurz: > The KVM_MAX_VCPUS define provides the maximum number of vCPUs per guest, and > also the upper limit for vCPU ids. This is okay for all archs except PowerPC > which can have higher ids, depending on the cpu/core/thread topology. In the > worst case (single

Re: [PATCH v5 2/2] kvm: introduce KVM_MAX_VCPU_ID

2016-05-03 Thread Greg Kurz
On Tue, 3 May 2016 08:49:12 +0200 Cornelia Huck wrote: > On Tue, 03 May 2016 06:52:02 +0200 > Greg Kurz wrote: > > > The KVM_MAX_VCPUS define provides the maximum number of vCPUs per guest, and > > also the upper limit for vCPU ids. This is

Re: [PATCH v5 2/2] kvm: introduce KVM_MAX_VCPU_ID

2016-05-03 Thread Greg Kurz
On Tue, 3 May 2016 08:49:12 +0200 Cornelia Huck wrote: > On Tue, 03 May 2016 06:52:02 +0200 > Greg Kurz wrote: > > > The KVM_MAX_VCPUS define provides the maximum number of vCPUs per guest, and > > also the upper limit for vCPU ids. This is okay for all archs except PowerPC > > which can have

Re: [PATCH v5 2/2] kvm: introduce KVM_MAX_VCPU_ID

2016-05-03 Thread Cornelia Huck
On Tue, 03 May 2016 06:52:02 +0200 Greg Kurz wrote: > The KVM_MAX_VCPUS define provides the maximum number of vCPUs per guest, and > also the upper limit for vCPU ids. This is okay for all archs except PowerPC > which can have higher ids, depending on the

Re: [PATCH v5 2/2] kvm: introduce KVM_MAX_VCPU_ID

2016-05-03 Thread Cornelia Huck
On Tue, 03 May 2016 06:52:02 +0200 Greg Kurz wrote: > The KVM_MAX_VCPUS define provides the maximum number of vCPUs per guest, and > also the upper limit for vCPU ids. This is okay for all archs except PowerPC > which can have higher ids, depending on the cpu/core/thread topology. In the > worst

[PATCH v5 2/2] kvm: introduce KVM_MAX_VCPU_ID

2016-05-02 Thread Greg Kurz
The KVM_MAX_VCPUS define provides the maximum number of vCPUs per guest, and also the upper limit for vCPU ids. This is okay for all archs except PowerPC which can have higher ids, depending on the cpu/core/thread topology. In the worst case (single threaded guest, host with 8 threads per core),

[PATCH v5 2/2] kvm: introduce KVM_MAX_VCPU_ID

2016-05-02 Thread Greg Kurz
The KVM_MAX_VCPUS define provides the maximum number of vCPUs per guest, and also the upper limit for vCPU ids. This is okay for all archs except PowerPC which can have higher ids, depending on the cpu/core/thread topology. In the worst case (single threaded guest, host with 8 threads per core),