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

RE: [Xen-devel] Problems with enabling hypervisor C and P-statecontrol

>From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx] 
>Sent: Monday, October 27, 2008 7:25 PM
>On 27/10/08 07:56, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:
>> Also how about BSP? If BSP is not thread0/core0/package0,
>> then all the rest sorting effort is just meaningless. :-(
>True. Another possibility would be to provide a remapping between CPU
>identifiers used within Xen and those exposed to tools via 
>The latter could be sorted; and no ordering constraints placed on the

This looks better, but the place to be changed would be large.
Hypercall handlers are easy. However carefulness has to be
paid for some implicit paths, like xentrace and serial output,
where smp_processor_id() is invoked naturally. Such info can
be inconsistent to identifiers exposed via sysctl/domctl, when 
consumed by user or developer. Then another level of translation
between these two  are required to be exposed again.

If anyway we'll add a new path to expose mapping between xen 
identifier and physical topology, above requirement seems not 
strong then. :-)

Xen-devel mailing list



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