[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] xenstored.h


  • To: "Rik van Riel" <riel@xxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Mon, 12 Sep 2005 12:32:51 -0700
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 12 Sep 2005 19:30:50 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcW30GFMhmyxwN3UT4+bRU1lgZO9IQAABrjQ
  • Thread-topic: [Xen-devel] xenstored.h

Currently, there are many files in xen/include/public that
are necessary to build xenlinux.  The mkbuildtree process
moves (links?) them to linux/include/asm-xen/xen-public
prior to building linux.

I assume once the API churn settles down, there will need
to be some kind of extra version control to ensure that
these stay sync'd. 

> -----Original Message-----
> From: Rik van Riel [mailto:riel@xxxxxxxxxx] 
> Sent: Monday, September 12, 2005 1:29 PM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] xenstored.h
> 
> On Mon, 12 Sep 2005, Magenheimer, Dan (HP Labs Fort Collins) wrote:
> 
> > Now that xenstore is in the mainline and xenstored.h is
> > part of the API to xenlinux, should xenstored.h be
> > moved into xen/include/public instead of being
> > mkbuildtree'd from tools/xenstore to drivers/xen/xenbus?
> 
> Won't that make it impossible to build xenolinux kernels
> outside of the Xen tree - say, kernel RPMs ?
> 
> -- 
> All Rights Reversed
> 

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.