From mboxrd@z Thu Jan  1 00:00:00 1970
From: Igor Mammedov <imammedo@redhat.com>
Subject: Re: [PATCH v4 2/2] KVM: move vcpu id checking to archs
Date: Fri, 22 Apr 2016 13:19:57 +0200
Message-ID: <20160422131957.6419a696@nial.brq.redhat.com>
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: QUOTED-PRINTABLE
Cc: Radim =?UTF-8?B?S3LEjW3DocWZ?= <rkrcmar@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>, james.hogan@imgtec.com,
	mingo@redhat.com, linux-mips@linux-mips.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	David Hildenbrand <dahi@linux.vnet.ibm.com>,
	qemu-ppc@nongnu.org, Cornelia Huck <cornelia.huck@de.ibm.com>,
	Paul Mackerras <paulus@samba.org>,
	David Gibson <david@gibson.dropbear.id.au>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <20160422112538.41b23a9d@bahia.huguette.org>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On Fri, 22 Apr 2016 11:25:38 +0200
Greg Kurz <gkurz@linux.vnet.ibm.com> wrote:

> Hi Radim !
>=20
> On Thu, 21 Apr 2016 19:36:11 +0200
> Radim Kr=C4=8Dm=C3=A1=C5=99 <rkrcmar@redhat.com> wrote:
>=20
> > 2016-04-21 18:45+0200, Greg Kurz: =20
> > > On Thu, 21 Apr 2016 18:00:19 +0200
> > > Radim Kr=C4=8Dm=C3=A1=C5=99 <rkrcmar@redhat.com> wrote:   =20
> > >> 2016-04-21 16:20+0200, Greg Kurz:   =20
[...]
> > >                                                                  =
    maybe later
> > > if we have other scenarios where vcpu ids need to cross the limit=
 ?   =20
> >=20
> > 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 probabl=
y
> > won't be improved to actually scale, so MAX_CPUS will remain lower.
> > =20
That's not true, x86 is going to stick with KVM_MAX_VCPUS/qemu's max_cp=
us,
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.
=20
>=20
> Do you have some pointers to share so that we can see the broader pic=
ture ?
>=20
> Thanks !
>=20
> --
> Greg
>=20
> --
> 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