On 11/12/14 18:19, Matt Wilson wrote:
> On Wed, Dec 10, 2014 at 10:36:18AM +0000, Andrew Cooper wrote:
>> On 10/12/14 06:00, Matt Wilson wrote:
>>> That's not strictly true. You can use the processor index in ACPI.
>> The LAPIC objects in the MADT/APIC table?  That is still constructed
>> with the broken LAPIC_ID = 2 * processor_id logic.
> Have you checked on an EC2 instance (for example: C3, I2, R3)?

I meant in terms of upstream code.  I will believe you when you say that
those instances do it differently.

My point was that the processor index is only as accurate as hvmloader
makes it, and upstream, this relies on the broken logic.

Even if hvmloader is altered and does things differently, it is still
bogus to draw any inference of vcpu_id from processor id.

~Andrew


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Reply via email to