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] scheduler independent forced vcpu selection

To: Ryan Harper <ryanh@xxxxxxxxxx>
Subject: Re: [Xen-devel] scheduler independent forced vcpu selection
From: Stephan Diestelhorst <sd386@xxxxxxxxxxxx>
Date: Thu, 19 May 2005 14:25:09 +0100
Cc: Stephan Diestelhorst <Stephan.Diestelhorst@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 19 May 2005 13:24:35 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050518223744.GL7305@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20050517204832.GH7305@xxxxxxxxxx> <428B30BC.8070602@xxxxxxxxxxxx> <20050518223744.GL7305@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)
Ryan Harper schrieb:
> * Stephan Diestelhorst <sd386@xxxxxxxxxxxx> [2005-05-18 09:04]:
> 
>>>I'm working on a new hypercall, do_confer, which allows the directed
>>>yielding of a vcpu to another vcpu.  It is mainly used when a vcpu fails
>>>to acquire a spinlock, yielding to the lock holder instead of spinning. I
>>>ported the ppc64 spinlock implementation for the i386 linux portion.  In
>>>implementing the hypercall, I've been trying to figure out how to get
>>>the scheduler (I've only played with bvt) to run the vcpu passed in the
>>>hypercall (after some validation) but I've run into various bad state
>>>situations (do_softirq pending != 0 assert, '!active_ac_timer(timer)'
>>>failed , and __task_on_runqueue(prev) failed) which tells me I
>>>don't fully understand all of the book-keeping that is needed.  Has
>>>anyone thought about how to do this with either BVT or the new EDF
>>>scheduler?
> 
> 
> After some thought, domain_wake(), followed by
> raise_softirq(SCHEDULE_SOFTIRQ) does what I want and removes the huge
> mess I was making in __enter_scheduler().  

Are you waking up the domain that holds the lock? Then you would rely on
the scheduler to give the woken domain a high "priority" (whatever this
means for the current scheduler) and should start that domain
immediatelly, right?

Best,
  Stephan

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