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

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Xen-devel] Re: Xen: Hybrid extension patchset for hypervisor

from [Jeremy Fitzhardinge] [Permanent Link][Original]
To: "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: Xen: Hybrid extension patchset for hypervisor
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Fri, 18 Sep 2009 17:28:34 -0700
Cc: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, "Yang, Sheng" <sheng.yang@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Dong, Eddie" <eddie.dong@xxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>
Delivery-date: Fri, 18 Sep 2009 17:28:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <0B53E02A2965CE4F9ADB38B34501A3A19411EAE7@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C6D66994.14D6A%keir.fraser@xxxxxxxxxxxxx> <C6D6AEEA.14EBF%keir.fraser@xxxxxxxxxxxxx> <0B53E02A2965CE4F9ADB38B34501A3A1940C78A8@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4AB12C1F.9080502@xxxxxxxx> <1253135571.3896.4873.camel@xxxxxxxxxxxxxxxxxxxxx> <4AB15707.20305@xxxxxxxx> <1253178985.16152.26.camel@xxxxxxxxxxxxxxxxxxxxxx> <0B53E02A2965CE4F9ADB38B34501A3A1940C840B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4AB2733B.6060804@xxxxxxxx> <0B53E02A2965CE4F9ADB38B34501A3A19411EAE7@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Lightning/1.0pre Thunderbird/3.0b3 
On 09/18/09 17:17, Nakajima, Jun wrote:
> Even if we start from PV kernels, I think what we should do is to implement 
> ability (as "incremental changes") for PV guests to stop using PV MMU (and PV 
> CPU) at boot time depending on the H/W features available rather than to keep 
> using the same ABI, because we may not need them in the near future. Then, 
> such PV kernels would be at par or faster/more efficient than pure HVM guests 
> on machines with HAP enabled because of the other PV features. 
>   

Sure, that's no problem.  So long as the current ABI keeps working, we
can easily switch to something else more appropriate where possible.

    J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [Xen-devel] Re: pv_ops dom0 attempt, Jeremy Fitzhardinge
Next by Date:  Re: [Xen-devel] Re: pvclock in userland (reprise), Jeremy Fitzhardinge
Previous by Thread:  RE: [Xen-devel] Re: Xen: Hybrid extension patchset for hypervisor, Nakajima, Jun
Next by Thread:  Re: [Xen-devel] Re: Xen: Hybrid extension patchset for hypervisor, Jeremy Fitzhardinge
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy