[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Real-time support


  • To: "Ky Srinivasan" <ksrinivasan@xxxxxxxxxx>
  • From: "Geoffrey Lefebvre" <geoffrey@xxxxxxxxx>
  • Date: Tue, 8 May 2007 13:39:24 -0700
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 08 May 2007 13:37:47 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=XAjgJ2skEIYlVcLBbCADUuvfVW0MJSfd1copj/yXqy+hZjdyWQABpb/U17Xm9dKk04uf5nY2AXiyX81aZgKZpkyhj0aanfPrymUg+gGnz7riTZjh5D3nvWPmIlssZvqPvUJ/pCbZSHCoiuP1G8qwKgRnrFU4jCHTJTSyfvIzZMg=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,

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.

cheers,

geoffrey







On 5/8/07, Ky Srinivasan <ksrinivasan@xxxxxxxxxx> wrote:
Since execution sequence within the hypervisor is non-preemptable,  is there an 
upper bound on time that can be spent in the hypervisor?

Thanks,

K. Y



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


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.