From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <jbeulich@novell.com>
Subject: RE: [PATCH 1/9] tmem: Public interface for tmem
Date: Fri, 06 Feb 2009 14:30:43 +0000
Message-ID: <498C57A3.76E4.0078.0@novell.com>
References: <498C06FC.76E4.0078.0@novell.com>
	<8c5a926b-f422-41d0-b709-72b0360e341f@default>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <8c5a926b-f422-41d0-b709-72b0360e341f@default>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

>>> Dan Magenheimer <dan.magenheimer@oracle.com> 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.

Jan