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

Re: [Xen-devel] [PATCH] x86, hvm: document the de facto policy for vCPU ids

To: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>
From: Konrad Rzeszutek Wilk <konrad@xxxxxxxxxx>
Date: Tue, 12 Jul 2016 12:28:02 -0400
Cc: Tim Deegan <tim@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Wei Liu <wei.liu2@xxxxxxxxxx>, George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Ian Jackson <ian.jackson@xxxxxxxxxxxxx>, Xen Devel Mailing list <xen-devel@xxxxxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>
Delivery-date: Tue, 12 Jul 2016 16:28:06 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On Tue, Jul 12, 2016 at 7:44 AM, Vitaly Kuznetsov <vkuznets@xxxxxxxxxx> wrote:
> PVHVM guests may need to know Xen's idea of vCPU ids they have and the
> only way they can figure them out is to use ACPI ids from MADT table.
> Document the de facto policy.
>
> Signed-off-by: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>

Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>

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

Follow-Ups:
- Re: [Xen-devel] [PATCH] x86, hvm: document the de facto policy for vCPU ids
  - From: Andrew Cooper

References:
- [Xen-devel] [PATCH] x86, hvm: document the de facto policy for vCPU ids
  - From: Vitaly Kuznetsov

Prev by Date: Re: [Xen-devel] [PATCH v6] x86/mem-sharing: mem-sharing a range of memory
Next by Date: Re: [Xen-devel] [PATCH] vmx/monitor: CPUID events
Previous by thread: [Xen-devel] [PATCH] x86, hvm: document the de facto policy for vCPU ids
Next by thread: Re: [Xen-devel] [PATCH] x86, hvm: document the de facto policy for vCPU ids
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.