WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

> > > + HYPERVISOR_shared_info = (struct shared_info *)shared_info_page;
> > > +
> > > + /* Don't do the full vcpu_info placement stuff until we have a
> > > +    possible map and a non-dummy shared_info. */
> > 
> > Might want to mention where the full vpcu placement is done.
> 
> The comment is not accurate, we actually don't do any vcpu_info
> placement on hvm because it is not very useful there.
> Better just to remove the comment (I have done so in my tree).
> 
> > > + per_cpu(xen_vcpu, 0) = &HYPERVISOR_shared_info->vcpu_info[0];
> > 
So.. what is the purpose of the per_cpu(xen_vcpu, 0) then?

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel