Re: [Xen-devel] [PATCH 02/12] early PV on HVM

From: Jeremy Fitzhardinge
Date: Tue Jun 08 2010 - 12:09:42 EST

On 06/08/2010 06:46 AM, Konrad Rzeszutek Wilk wrote:
>>>> + per_cpu(xen_vcpu, 0) = &HYPERVISOR_shared_info->vcpu_info[0];
> So.. what is the purpose of the per_cpu(xen_vcpu, 0) then?

We still need the percpu info for things like time, but it is mapped out
of the platform device rather than placed at any address we want in
kernel memory (vcpu info placement), where we can access it directly as
a percpu variable. This is only really relevent for the implementation
of the interrupt enable/disable pvops, so it doesn't matter for hvm.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at