From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH 6/10] Allow vcpu to pause self Date: Wed, 11 Jul 2007 18:02:23 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Tian, Kevin" Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 27/6/07 14:37, "Tian, Kevin" 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 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