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

[Xen-devel] Re: [PATCH] txt: 2/6 - explicitly protect TXT addr ranges fr

To: "Cihula, Joseph" <joseph.cihula@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "xense-devel@xxxxxxxxxxxxxxxxxxx" <xense-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH] txt: 2/6 - explicitly protect TXT addr ranges from dom0
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 21 Jan 2009 08:09:36 +0000
Cc: "Wang, Shane" <shane.wang@xxxxxxxxx>
Delivery-date: Wed, 21 Jan 2009 00:09:32 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4F65016F6CB04E49BFFA15D4F7B798D92D699EC6@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acl6wsxj6VC8E6tgRhOE8Ctp6+7wEQAGlCg5ABXGpGAAGthzAA==
Thread-topic: [PATCH] txt: 2/6 - explicitly protect TXT addr ranges from dom0
User-agent: Microsoft-Entourage/12.15.0.081119
On 21/01/2009 07:41, "Cihula, Joseph" <joseph.cihula@xxxxxxxxx> wrote:

> We had an earlier version of our patch that just altered the e820 table, but
> we were concerned about the code complexity needed to do that (the existing
> Xen e820 fns aren¹t sufficient for this).  Here is the change that we would
> need to add?do you prefer this:

Well, I'm not sure about the implementation in e820.c, but still I prefer
this approach overall. Go with this approach and I'll clean up the e820.c
parts myself if I can think of a simpler way to implement this mechanism.

 -- Keir



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

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