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-research

[Xen-research] Custom Xen Real-Time Scheduler

To: <xen-research@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-research] Custom Xen Real-Time Scheduler
From: "Paul Harvey" <stockingpaul@xxxxxxxxxxx>
Date: Thu, 18 Jun 2009 19:46:32 +0100
Delivery-date: Thu, 18 Jun 2009 11:49:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-research-request@lists.xensource.com?subject=help>
List-id: Research Issues on Xen <xen-research.lists.xensource.com>
List-post: <mailto:xen-research@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-research>, <mailto:xen-research-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-research>, <mailto:xen-research-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-research-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcnvnILnQjI4MYtURaGXqVuD7Xv55A==

Hi All,

 

I am beginning work on a real time scheduler for Xen. I am wanting to prioritise which domain to run on the outstanding time before a domain will be interrupted, either by the periodic timer in Xen or any outstanding one shot timers that the domain has registered.

 

I have just started and i was wondering if someone could give me an overview of the one shot timer process, ie where the hypercall enters the kernel and stores the outstanding requests from the domains.

 

I realise that this may be obvious to people out there who know the code backwards however as i have just started it is a little daunting at the moment.

 

Thanks

Paul

_______________________________________________
Xen-research mailing list
Xen-research@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-research