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/
Home Products Support Community News


RE: [Xen-devel] [PATCH 1/9] tmem: Public interface for tmem

To: "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH 1/9] tmem: Public interface for tmem
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Fri, 06 Feb 2009 14:30:43 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 06 Feb 2009 06:30:22 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <8c5a926b-f422-41d0-b709-72b0360e341f@default>
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: <498C06FC.76E4.0078.0@xxxxxxxxxx> <8c5a926b-f422-41d0-b709-72b0360e341f@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> 06.02.09 15:08 >>>
>> Couldn't the whole second hunk rather go in a separate header?
>Are you referring to the constants and the data structure?
>All of these are used by both xen and a guest and must
>be identical, thus the placement in public/xen.h.  Are there
>other header files which are guaranteed to be shared between
>xen and a (linux) guest?

All headers in xen/include/public/. You could create a new one, or (less
ideal) put it in xen/include/public/memory.h.


Xen-devel mailing list

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