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

RE: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 --nonew issue


  • To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, "Li, Haicheng" <haicheng.li@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
  • Date: Thu, 27 Mar 2008 10:43:43 +0800
  • Delivery-date: Wed, 26 Mar 2008 19:45:53 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AciNk+8gVPQ6UlY+Q3imHZ2zMFtzTQA1gPlyAC47q+AAAVK7zwALrhHtABdPkbA=
  • Thread-topic: [Xen-devel] VMX status report. Xen: #17270 & Xen0: #488 --nonew issue

Keir Fraser wrote:
> 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

Really great!

-- Dexuan

_______________________________________________
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®.