Re: KVM_MAX_VCPU hard limit of 255 on x86

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2016-04-04 21:14+0200, Igor Mammedov:
> On Mon, 4 Apr 2016 17:17:19 +0200
> Radim Krčmář <rkrcmar@xxxxxxxxxx> wrote:
>>                                                 another blocker is
>> that QEMU cannot handle more than 255 VCPUs, mainly because of its AML
>> generator.  Igor (Cc'd) knows more about the status of ACPI.
> I'm going to post patches that enable more than 255 VCPUs
> on ACPI side of QEMU once development window for 2.7 opens.

Great, thanks!

>> (And firmware doesn't implement x2APIC, and other minor problems ...)
> Firmware probably doesn't need more than 1 VCPU, maybe we can
> get rid of if it enumerating VCPUs via broadcast AP wakeup
> since it no longer builds ACPI tables anymore.
> 
> It should save some boot time due to removing timeout for waiting
> APs wakeup.

Rudimentary x2APIC support is needed, because the OS should get control
with all LAPICs in x2APIC mode when any APIC ID is over 255.
We could code that in QEMU to save some time, but I am reluctant to move
the whole MP initialization before >255 is proven as working. :)

>> All pieces should be in place within half a year, though.
>> The next hard limit is ~2^20 or ~2^32.
> In current version of my ACPI patches it's 2^32 limit so far.

Perfect.  (2^16-1)*16 would be a limit only if some major OS didn't want
understand that logical addressing doesn't work beyond that ...
(Which shouldn't happen.)
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux