Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752782AbcDVLUG (ORCPT ); Fri, 22 Apr 2016 07:20:06 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38140 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751897AbcDVLUC convert rfc822-to-8bit (ORCPT ); Fri, 22 Apr 2016 07:20:02 -0400 Date: Fri, 22 Apr 2016 13:19:57 +0200 From: Igor Mammedov To: Greg Kurz Cc: Radim =?UTF-8?B?S3LEjW3DocWZ?= , Paolo Bonzini , james.hogan@imgtec.com, mingo@redhat.com, linux-mips@linux-mips.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, David Hildenbrand , qemu-ppc@nongnu.org, Cornelia Huck , Paul Mackerras , David Gibson Subject: Re: [PATCH v4 2/2] KVM: move vcpu id checking to archs Message-ID: <20160422131957.6419a696@nial.brq.redhat.com> In-Reply-To: <20160422112538.41b23a9d@bahia.huguette.org> References: <146124809455.32509.15232948272580716135.stgit@bahia.huguette.org> <146124811255.32509.17679765789502091772.stgit@bahia.huguette.org> <20160421160018.GA31953@potion> <20160421184500.6cb5fd8a@bahia.huguette.org> <20160421173611.GB30356@potion> <20160422112538.41b23a9d@bahia.huguette.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1336 Lines: 37 On Fri, 22 Apr 2016 11:25:38 +0200 Greg Kurz wrote: > Hi Radim ! > > On Thu, 21 Apr 2016 19:36:11 +0200 > Radim Krčmář wrote: > > > 2016-04-21 18:45+0200, Greg Kurz: > > > On Thu, 21 Apr 2016 18:00:19 +0200 > > > Radim Krčmář wrote: > > >> 2016-04-21 16:20+0200, Greg Kurz: [...] > > > maybe later > > > if we have other scenarios where vcpu ids need to cross the limit ? > > > > x86 is going to have that soon too -- vcpu_id will be able to range from > > 0 to 2^32-1 (or 2^31), but MAX_CPUS related data structures probably > > won't be improved to actually scale, so MAX_CPUS will remain lower. > > That's not true, x86 is going to stick with KVM_MAX_VCPUS/qemu's max_cpus, the only thing that is going to change is that max supported APIC ID value will be in range 0 to 2^32-1 vs current 8bit one and since APIC ID is not vcpu_id so it won't affect vcpu_id. > > Do you have some pointers to share so that we can see the broader picture ? > > Thanks ! > > -- > Greg > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html