Re: [PATCH 0/4] KVM: add KVM_CREATE_VM2 to allow dynamic kvm->vcpus array

2017-04-24 Thread Radim Krčmář
2017-04-18 14:29+0200, Cornelia Huck: > On Tue, 18 Apr 2017 13:11:55 +0200 > David Hildenbrand wrote: >> On 13.04.2017 22:19, Radim Krčmář wrote: >> > new KVM_MAX_CONFIGURABLE_VCPUS, probably directly to INT_MAX/KVM_VCPU_ID, >> > so we >> > don't have to worry about it for a while. >> > >> > PPC

Re: [PATCH 0/4] KVM: add KVM_CREATE_VM2 to allow dynamic kvm->vcpus array

2017-04-24 Thread Radim Krčmář
2017-04-18 13:11+0200, David Hildenbrand: > On 13.04.2017 22:19, Radim Krčmář wrote: >> The basic idea is to let userspace provide the desired maximal number of >> VCPUs and allocate only necessary memory for them. >> >> The goal is to freeze KVM_MAX_VCPUS at its current level and only increase >

Re: [PATCH 0/4] KVM: add KVM_CREATE_VM2 to allow dynamic kvm->vcpus array

2017-04-18 Thread Cornelia Huck
On Tue, 18 Apr 2017 13:11:55 +0200 David Hildenbrand wrote: > On 13.04.2017 22:19, Radim Krčmář wrote: > > The basic idea is to let userspace provide the desired maximal number of > > VCPUs and allocate only necessary memory for them. > > > > The goal is to freeze KVM_MAX_VCPUS at its current le

Re: [PATCH 0/4] KVM: add KVM_CREATE_VM2 to allow dynamic kvm->vcpus array

2017-04-18 Thread David Hildenbrand
On 13.04.2017 22:19, Radim Krčmář wrote: > The basic idea is to let userspace provide the desired maximal number of > VCPUs and allocate only necessary memory for them. > > The goal is to freeze KVM_MAX_VCPUS at its current level and only increase the KVM_MAX_VCPUS might still increase e.g. if hw