[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Explore the source code
- To: xen-devel@xxxxxxxxxxxxxxxxxxx
- From: Marco Tizzoni <marco.tizzoni@xxxxxxxxx>
- Date: Wed, 1 Apr 2009 09:28:13 +0200
- Delivery-date: Wed, 01 Apr 2009 00:28:58 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ro9MVPp458S4sys6fE/06ZlVPWO9xwDDDMK0EY0iRyWkh8vE117WwqeCiGqC6BwPOn bMkzcFYQAgABeRxGMwkmKLU5luXOi+VkR0Ynn7TMDbk0ImaZSuTDNk4M8AVOP4Gwk5oL A8O0FWD6MdTyUfYnaunl9hYlJAMd0hsDLT4p4=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
On Tue, Mar 31, 2009 at 12:40 PM, George Dunlap <dunlapg@xxxxxxxxx> wrote:
Hey Marco,
Sorry for not following up. I think the scheduler is pretty well
contained in the following files:
xen/common/schedule.c
xen/common/sched_credit.c
xen/include/xen/sched.h
One thing to note about Xen that's different than Linux is that while
in Linux there's a per-process kernel stack, in Xen there's no per-VM
hypervisor stack. When schedule() is called, it completely throws away
all hypervisor stack and context, and returns directly to the target
VM. For this reason, schedule() is never called directly, but a
schedule softirq is raised and called on the way back out of the
hypervisor anyway.
Thanks for your answer, with your help and David's book how to implement a new scheduler it's pretty clear now.
Also I'd have a look to device scheduling in order change its behaviour according to my new scheduler policies. Any suggestion on where to start?
Marco
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
