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] credit scheduler and HYPERVISOR_yield()

To: John Levon <levon@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] credit scheduler and HYPERVISOR_yield()
From: Emmanuel Ackaouy <ackaouy@xxxxxxxxx>
Date: Sun, 14 Oct 2007 23:25:43 +0200
Cc: George Dunlap <gdunlap@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 14 Oct 2007 14:26:12 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:content-transfer-encoding:cc:from:subject:date:to:x-mailer; bh=WrquXRD/xYbfbE/6XUjTUW3OKM9Fsg0le6WMggt+ePY=; b=htkmW5iU0AtChSQGM0RzYwjxt10WuKD2vbdoFhXlQ8+tWWBAmZomUkMDtl7/fUgt5PcTt5YGOvjI1LJds/a8/16rp+/LVro5cqu7eqmjlMMdtOIeHotu4/frR+LusB0eClI1yheIR5AK/nGsGfkd0w7WG3iQKGsNIIOCYu8AfAs=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:in-reply-to:references:mime-version:content-type:message-id:content-transfer-encoding:cc:from:subject:date:to:x-mailer; b=UtYRWqmeTLWQyb9YDtTgi+mZr6jM5srxVpC2CSudtVrnjNnm8hNPXMSwTUHnjWBJE+WI6vyBHQNQ3nAid78z+XitRPw9MyHKnfdEG7IZp955FvVoAqTnPWk2YWjgVMxLMAf+7a1jbVkIhV8zIQAwFds7SOHCKNqzDRhJ67vLHW4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071014194933.GC16827@xxxxxxxxxxxxxxxxxxxxxxx>
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: <20071008234118.GA1396@xxxxxxxxxxxxxxxxxxxxxxx> <7e903d73fbea1bb8ca97396fef058b2b@xxxxxxxxx> <20071009121533.GA30258@xxxxxxxxxxxxxxxxxxxxxxx> <de76405a0710090622x63a1c34exc7a14c391782211b@xxxxxxxxxxxxxx> <20071014184528.GB16827@xxxxxxxxxxxxxxxxxxxxxxx> <d7a896adb8c075492604f52f257dd573@xxxxxxxxx> <20071014194933.GC16827@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Oct 14, 2007, at 21:49, John Levon wrote:
On Sun, Oct 14, 2007 at 09:20:50PM +0200, Emmanuel Ackaouy wrote:
Why can't you initiate the IPI to all the destination CPUs first

We do, maybe I misunderstood what you were suggesting.

Thats ok. I still don't understand what problem you're working
on myself. I think you're suggesting you'd like to always
deschedule a VCPU initiating an IPI for potentially multiple
time slices. That seems crazy to me.


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