xen-devel

[Top] [All Lists]

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

from [Dan Magenheimer]

[Permanent Link][Original]

To:	Jan Beulich <jbeulich@xxxxxxxxxx>
Subject:	RE: [Xen-devel] [PATCH 1/9] tmem: Public interface for tmem
From:	Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date:	Fri, 6 Feb 2009 06:08:54 -0800 (PST)
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Fri, 06 Feb 2009 06:10:04 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<498C06FC.76E4.0078.0@xxxxxxxxxx>
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

Thanks for the feedback!

> 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?

Thanks,
Dan

> -----Original Message-----
> From: Jan Beulich [mailto:jbeulich@xxxxxxxxxx]
> Sent: Friday, February 06, 2009 1:47 AM
> To: Dan Magenheimer
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] [PATCH 1/9] tmem: Public interface for tmem
> 
> 
> >>> Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> 06.02.09 01:40 >>>
> >[1] Public interface for tmem
> 
> Couldn't the whole second hunk rather go in a separate header?
> 
> Jan
> 
>

_______________________________________________
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>
[Xen-devel] [PATCH 1/9] tmem: Public interface for tmem, Dan Magenheimer Re: [Xen-devel] [PATCH 1/9] tmem: Public interface for tmem, Jan Beulich RE: [Xen-devel] [PATCH 1/9] tmem: Public interface for tmem, Dan Magenheimer <= RE: [Xen-devel] [PATCH 1/9] tmem: Public interface for tmem, Jan Beulich

Previous by Date:	Re: [Xen-devel] [PATCH 3/5] setup_irq/request_irq/free_irq fixups, Espen Skoglund
Next by Date:	RE: [Xen-devel] [PATCH 8/9] tmem: invocations of tmem code fromexisting xen code, Dan Magenheimer
Previous by Thread:	Re: [Xen-devel] [PATCH 1/9] tmem: Public interface for tmem, Jan Beulich
Next by Thread:	RE: [Xen-devel] [PATCH 1/9] tmem: Public interface for tmem, Jan Beulich
Indexes:	[Date] [Thread] [Top] [All Lists]