[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160425141522.GB2386@potion>
Date: Mon, 25 Apr 2016 16:15:22 +0200
From: Radim Krčmář <rkrcmar@...hat.com>
To: Greg Kurz <gkurz@...ux.vnet.ibm.com>
Cc: Paolo Bonzini <pbonzini@...hat.com>, james.hogan@...tec.com,
mingo@...hat.com, linux-mips@...ux-mips.org, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org,
David Hildenbrand <dahi@...ux.vnet.ibm.com>,
qemu-ppc@...gnu.org, Cornelia Huck <cornelia.huck@...ibm.com>,
Paul Mackerras <paulus@...ba.org>,
David Gibson <david@...son.dropbear.id.au>
Subject: Re: [PATCH v4 2/2] KVM: move vcpu id checking to archs
2016-04-22 16:50+0200, Greg Kurz:
> Just to be sure I haven't missed something:
> - change the spec to introduce the MAX_VCPU_ID concept
> - update all related checks in KVM
> - provide a KVM_CAP_MAX_VCPU_ID for userspace
That is it, thanks a lot!
(From nitpicks that come to my mind ... MAX_VCPU_ID should not be able
to lower the VCPU_ID limit below MAX_VCPUS.)
Powered by blists - more mailing lists