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

Re: [Xen-devel] Vcpu allocation for a newly created domU

> >> smp_processor_id() and current->processor should match in
> >> __context_switch().
> > need not be..cant the scheduler schedule the vcpu on a cpu other than
> > the cpu its currently running on...??
> When you enter the scheduler (and also __context_switch) you are  
> running VCPU=current on CPU=smp_processor_id().
this is true only if current is not set to the next vcpu. but if you
look at context_switch() just before calling __context_switch ,
set_curent(next) is done. At this point current is actually the next
vcpu to be scheduled. 

>  At this point in time  
> current->processor and smp_processor_id() will match.
So vcpu->processor need not match smp_processor_id()....


Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 


Xen-devel mailing list



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