Re: Enable more than 255 VCPU support without irq remapping function in the guest

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

 



2016-04-28 08:54+0200, Jan Kiszka:
> On 2016-04-28 03:11, Yang Zhang wrote:
>> On 2016/4/27 17:45, Jan Kiszka wrote:
>>> On 2016-04-27 11:39, Yang Zhang wrote:
>>>> I mean in Tianyu's case, if he doesn't care about to deliver external
>>>> interrupt to CPU >255, IR is not required.
>>>
>>> What matters is the guest OS. See my other reply on this why this
>>> doesn't work, even for Linux.
>> 
>> Since there only few devices in his case, set the irq affinity manually
>> is enough.

You could configure non-IPIs to work, but we want to create options that
are hard to break.

> Ah, wait - are we talking about emulating the Xeon Phi architecture in
> QEMU, accelerated by KVM?

Knights Landing will also be manufactured as a CPU, hopefully without
many peculiarities.

I think we are talking about extending KVM's IR-less x2APIC, when
standard x2APIC is the future.
--
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