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] Real-time support

To: "Geoffrey Lefebvre" <geoffrey@xxxxxxxxx>, "Ky Srinivasan" <ksrinivasan@xxxxxxxxxx>
Subject: RE: [Xen-devel] Real-time support
From: "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxx>
Date: Tue, 8 May 2007 21:56:44 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 08 May 2007 13:55:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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: <46403C69.E57C.0030.0@xxxxxxxxxx> <c3c918090705081339j2439155j30381e55c51ad418@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AceRsS9MHRXxgi04QuGVhWKdNcd9wgAAQGWw
Thread-topic: [Xen-devel] Real-time support
> I did some basic measurements on worst case execution time inside the
> hypervisor a while ago (6-8 months ago).  From what i remember, the
> worst case where between 1-2msec on a 3GHz P4.  This was under some
> load (make -j64 bzImage).  A big culprit was the mmu-ext hypercall
> which in certain cases recursively unpins a page table. Handling
> certain page faults also took a while. This was just a preliminary
> study so i didn't push the analysis very far.

The pin/unpin operations are certainly by far the longest running
operations in Xen, and it's been on the to-do list to make them
preemptable for a long time. This should be very simple as we can exit
the hypervisor leaving the EIP on the hypercall, and next time the guest
calls in we'll pick up where we left off. 

Anyone who cares about real time on x86 up for implementing this?


Ian

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

<Prev in Thread] Current Thread [Next in Thread>