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-ia64-devel

RE: [Xen-ia64-devel] [RFC][PATCH] [RESEND] support special guest optimis

To: "Dietmar Hahn" <dietmar.hahn@xxxxxxxxxxxxxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] [RFC][PATCH] [RESEND] support special guest optimisations in the hypervisor
From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
Date: Fri, 6 Jul 2007 09:01:14 +0800
Cc: Alex Williamson <alex.williamson@xxxxxx>
Delivery-date: Thu, 05 Jul 2007 17:59:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200707051232.43659.dietmar.hahn@xxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ace+79XLhW42yxfzQvepQVgScPZhVQAeNk5g
Thread-topic: [Xen-ia64-devel] [RFC][PATCH] [RESEND] support special guest optimisations in the hypervisor
>From: Dietmar Hahn [mailto:dietmar.hahn@xxxxxxxxxxxxxxxxxxx]
>Sent: 2007年7月5日 18:33
>To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Cc: Xu, Anthony; Alex Williamson
>Subject: Re: [Xen-ia64-devel] [RFC][PATCH] [RESEND] support special guest
>optimisations in the hypervisor
>
>Am Donnerstag, 5. Juli 2007 schrieb Dietmar Hahn:
>> Am Donnerstag, 5. Juli 2007 schrieb Xu, Anthony:
>> > I think you can do this way.
>> >
>> > A little concern,
>> > For dom0 & domU, pgprot and key are provided by guest, it is natural.
>> > While for HVM , pgprot and key are provided Xen, it is a little strange.
>>
>> Ok I understand, I will prepare a new patch.
>> Thanks.
>While thinking about the HVM part: should I only create an opt_feature
>#define OPTF_IDENT_MAP_HVM_REG4_5
>and simply replace the
>if (GOS_WINDOWS(v)
>by
>if (opt_feature & OPTF_IDENT_MAP_HVM_REG4_5)
>or should I do it the same way like on PV with setting pgprot and key
>(maybe this is overkill?) in the struct arch_domain and use these values
>during the optimization?
>Thanks.

Hi Dietmar,

I can understand you want to use the same interface for special guest 
Optimizations. While I think it is OK to use different interfaces for HVM and 
domU.
So I suggest HVM still use interface like GOS_WINDOWS(v), while domU uses 
opt_feature interface.

Thanks,
Anthony

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

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