From mboxrd@z Thu Jan  1 00:00:00 1970
From: Radim =?utf-8?B?S3LEjW3DocWZ?= <rkrcmar@redhat.com>
Subject: Re: Enable more than 255 VCPU support without irq remapping function
 in the guest
Date: Wed, 27 Apr 2016 16:38:10 +0200
Message-ID: <20160427143809.GA11780@potion>
References: <571F93CA.40200@intel.com>
 <571F9487.5090009@siemens.com>
 <20160426164939.GA18900@potion>
 <57205076.3000300@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Cc: Jan Kiszka <jan.kiszka@siemens.com>, pbonzini@redhat.com,
	kvm@vger.kernel.org, yang.zhang.wz@gmail.com, tglx@linutronix.de,
	gleb@redhat.com, mst@redhat.com, x86@kernel.org,
	Peter Xu <peterx@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>
To: Lan Tianyu <tianyu.lan@intel.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:56115 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751204AbcD0OiP (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 27 Apr 2016 10:38:15 -0400
Content-Disposition: inline
In-Reply-To: <57205076.3000300@intel.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

2016-04-27 13:39+0800, Lan Tianyu:
> On 2016=E5=B9=B404=E6=9C=8827=E6=97=A5 00:49, Radim Kr=C4=8Dm=C3=A1=C5=
=99 wrote:
>> 2016-04-26 18:17+0200, Jan Kiszka:
>>> On 2016-04-26 18:14, Lan, Tianyu wrote:
>>>> Hi All:
>>>>
>>>> Recently I am working on extending max vcpu to more than 256 on th=
e both
>>>> KVM/Xen. For some HPC cases, it needs many vcpus. The job requires=
 to
>>>> use X2APIC in the guest which supports 32-bit APIC id. Linux kerne=
l
>>>> requires irq remapping function during enabling X2APIC when max AP=
IC id
>>>> is more than 255(More detail please see try_to_enable_x2apic()).
>>=20
>> Our of curiosity, how many VCPUs are you aiming at?
>=20
> I think it's 1024.
>=20
> In the short term, we hope hypervisor at least supports 288 vcpus
> because Xeon phi chip already supports 288 logical cpus. As hardware
> development, there will be more logical cpus and we hope one guest ca=
n
> totally uses all cpu resources on the chip to meet HPC requirement.

Thanks, I think KVM will start by bumping the hard VCPU limit to 512 or
1024, with recommended maximum being 288.  You'll be able to raise the
hard limit just by configuing and recompiling.

>                             How about KVM X2APIC part? Do you have pa=
tch
> to extend KVM X2APIC to support 32-bit APIC ID?

I do, in limbo, as QEMU cannot create VCPUs with higher APIC IDs, yet.