From mboxrd@z Thu Jan 1 00:00:00 1970 From: Radim =?utf-8?B?S3LEjW3DocWZ?= Subject: Re: [PATCH v3] KVM: remove buggy vcpu id check on vcpu creation Date: Fri, 22 Apr 2016 15:07:06 +0200 Message-ID: <20160422130705.GD7202@potion> References: <146116689259.20666.15860134511726195550.stgit@bahia.huguette.org> <20160420182909.GB4044@potion> <20160421132958.0e9292d5@bahia.huguette.org> <20160421152916.GA30356@potion> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Greg Kurz , Paolo Bonzini , james.hogan@imgtec.com, Ingo Molnar , linux-mips@linux-mips.org, kvm , "linux-kernel@vger.kernel.org" , qemu-ppc@nongnu.org, Cornelia Huck , Paul Mackerras , David Gibson To: Wanpeng Li Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org 2016-04-22 09:40+0800, Wanpeng Li: > 2016-04-21 23:29 GMT+08:00 Radim Kr=C4=8Dm=C3=A1=C5=99 : >> x86 vcpu_id encodes APIC ID and APIC ID encodes CPU topology by >> reserving blocks of bits for socket/core/thread, so if core or threa= d >> count isn't a power of two, then the set of valid APIC IDs is sparse= , >=20 > ^^^^^^^^^^^^^^^^^^^ > ^^^^^^^ > Is this the root reason why recommand max vCPUs per vm is 160 and the > KVM_MAX_VCPUS is 255 instead of due to perforamnce concern? No, the recommended amout of VCPUs is 160 because I didn't bump it afte= r PLE stopped killing big guests. :/ You can get full 255 VCPU guest with a proper configuration, e.g. "-smp 255" or "-smp 255,cores=3D8" and the only problem is scalability, but I don't know of anything that doesn't scale to that point. (Scaling up to 2^32 is harder, because you don't want O(N) search, nor full allocation on smaller guests. Neither is a big problem now.)