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] change dom0 headers path

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] change dom0 headers path
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Thu, 20 Apr 2006 08:55:14 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, John Levon <levon@xxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 20 Apr 2006 06:55:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <f6b99d6b2ef717390f6ae100e1b87bf2@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20060420123936.GA840@xxxxxxxxxxxxxxxxxxxx> <f6b99d6b2ef717390f6ae100e1b87bf2@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mail/News 1.5 (X11/20060309)
Keir Fraser wrote:

On 20 Apr 2006, at 13:39, John Levon wrote:

Fairly obviously, we need to clean up the hard-coded "linux" names used
in includes. This is the first step in a number of changes around
letting dom0 build on something other than Linux.

What are the plans for these headers when the Linux kernel lives in some
place other than the xen tree itself? We'd like to be able to share the
structure definitions, but our ioctl values will differ from Linux's...

I'd prefer an interfacing library (or libraries) that can target Linux interfaces, Sun interfaces, etc. This would avoid inclusion of kernel interface headers outside that shim library.

Maybe this only needs to be done for evtchn interfaces. I would have hoped that libxenctrl and libxenguest would hide privcmd interfaces. I wonder why so many things include <linux/privcmd.h>?

Because libxc "leaks" a few of the dom0_op structures like dom0_getvcpuinfo_t, dom0_shadow_control_stats_t, etc in its public interface. This could be fixed by making sure all of those structures had wrapper (like xc_dominfo_t).


Anthony Liguori

 -- Keir

Xen-devel mailing list

Xen-devel mailing list