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] VMX status report. Xen: #17270 & Xen0: #488 -- nonew iss

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Li, Haicheng" <haicheng.li@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- nonew issue
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 26 Mar 2008 15:34:35 +0000
Delivery-date: Wed, 26 Mar 2008 09:28:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C40FCF29.1E53B%keir.fraser@xxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AciNk+8gVPQ6UlY+Q3imHZ2zMFtzTQA1gPlyAC47q+AAAVK7zwALrhHt
Thread-topic: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 -- nonew issue
User-agent: Microsoft-Entourage/11.4.0.080122
On 26/3/08 10:00, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx> wrote:

>> Keir, we checked guest installation with rhel4u3 today, we compared c/s
>> 17284 with c/s 16720,
>> The result shows latest c/s with mmio emulation changes is a little bit
>> faster than before on our test system with Xeon(r) processors, about 20
>> seconds faster.
> 
> That's pretty surprising! I found out that slowdown on my P4 system for
> WinXP installation is about 15%, so not as bad as I thought. And I can
> probably reclaim most of that performance loss.
> 
> I find it hard to explain a performance *win* though!

Well, I implemented a virtual-address to mmio-physical-address lookaside
cache for x86_emulate(), and with that I get following results for install
of WinXP (time is up to second reboot, after graphical part of install, from
an auto-install CD image):
 xen 3.2: 1 hour 20 minutes 23 seconds
 xen unstable using x86_emulate(): 1 hour 33 minutes 4 seconds
 xen unstable with new optimisation: 1 hour 12 minutes 57 seconds

Considering first result (Xen 3.2) as a baseline control experiment, basic
x86_emulate() mmio performance is 16% slower, while with the simple extra
optimisation I get a 10% speedup (so that's 22% speedup compared without the
optimisation).

Pretty nice!

 -- Keir



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