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

Re: [Xen-devel] x86's context switch ordering of operations


  • To: Jan Beulich <jbeulich@xxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Tue, 29 Apr 2008 17:52:51 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 29 Apr 2008 09:53:13 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AciqGXX1tFP0FhYMEd2kwQAWy6hiGQ==
  • Thread-topic: [Xen-devel] x86's context switch ordering of operations

On 29/4/08 16:37, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> Okay, that could be easily dealt with by doing set_current() explicitly
> in the switch-to-idle case, and moving it into __context_switch() in
> the other cases.

It wouldn't really help you. If you switch to from VCPU A to idle and then
to VCPU B, you would still end up calling ctxt_switch_from(A) when
current==idle.

> Any word on the significance of doing write_ptbase() after calling
> ctxt_switch_to()?

It probably could be done earlier.

 -- Keir



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


 


Rackspace

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