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

Re: [Xen-devel] [PATCH 6/10] Allow vcpu to pause self


  • To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Wed, 11 Jul 2007 18:02:23 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 11 Jul 2007 10:00:18 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Ace4wFEyWBrDMwUBRbudwW+SC7WIGwLHO6q6
  • Thread-topic: [Xen-devel] [PATCH 6/10] Allow vcpu to pause self

On 27/6/07 14:37, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:

> Add self pause ability, which is required by vcpu0/dom0 when
> running on a AP. This can't be satisfied by existing interface,
> since the new flag also serves as a sync point.
> 
> Signed-off-by Kevin Tian <kevin.tian@xxxxxxxxx>

I think this should not be needed. Why is dom0/vcpu0 special at all? If you
are doing the final work from a softirq context, can't dom0/vcpu0 simply be
paused like all others at that point? If not then we'll need to make some
arrangement using vcpu_set_affinity() - I won't add another flag on the
context-switch path.

So currently patches 6,7,9,10 are not applied. Patches 6 & 7 because they
need more iteration, as commented above. Patches 9 & 10 will likely change
when the platform_op hypercall interface is slimmed down, so I'm leaving
them out for now.

All other patches are in (although the platform_op interface part of patch 2
is disabled).

 -- 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®.