Xen devel - Sep 2005 - [PATCH][VT] add a directory for para-driver support in unmodified linux.

This patch adds a directory for para-driver support in unmodified linux.
The event channel is made to a pci device, the event is delivered by 
this device.
The build script will create the symbol link to linux-sparse tree for 
all the front end driver. A prinstine kernel path shall be given in
compile.sh.

Signed-off-by: Xiaofeng Ling <xiaofeng.ling@intel.com>
Signed-off-by: Arun Sharma <arun.sharma@intel.com>

  unmodified-sparse/Makefile                 |   33 ++++
  unmodified-sparse/README                   |   12 +
  unmodified-sparse/balloon/Makefile         |    2
  unmodified-sparse/blkfront/Makefile        |    8 +
  unmodified-sparse/compile.sh               |    2
  unmodified-sparse/evtchn-pci/Makefile      |   10 +
  unmodified-sparse/evtchn-pci/debuginfo.h   |   56 +++++++
  unmodified-sparse/evtchn-pci/evtchn-pci.c  |  330 
+++++++++++++++++++++++++++++++++++++++++++++++
  unmodified-sparse/evtchn-pci/evtchn-pci.h  |   91 ++++++++++++
  unmodified-sparse/evtchn-pci/evtchn.c      |  119 ++++++++++++++++
  unmodified-sparse/evtchn-pci/xen-support.c |   79 +++++++++++
  unmodified-sparse/include/asm/smp_alt.h    |    6
  unmodified-sparse/mkbuildtree              |   19 ++
  unmodified-sparse/netfront/Makefile        |    8 +
  unmodified-sparse/xenbus/Makefile          |   12 +
  15 files changed, 787 insertions(+)


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

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com 
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Ian Pratt
> Sent: 05 September 2005 09:02
> To: Xiaofeng Ling; Keir Fraser
> Cc: xen-devel
> Subject: [Xen-devel] RE: [PATCH][VT] add a directory for 
> para-driver support in unmodified linux.
> 
> > This patch adds a directory for para-driver support in unmodified 
> > linux.
> > The event channel is made to a pci device, the event is 
> delivered by 
> > this device.
> > The build script will create the symbol link to 
> linux-sparse tree for 
> > all the front end driver. A prinstine kernel path shall be given in 
> > compile.sh.
> 
> Does this follow ''best practice'' for building out of tree
> linux kernel modules? Or at least copy the build practice for 
> other common modules?
> 
> I don''t think its really a sparse tree, so we should probably 
> change the name.
> Perhaps ''hve-drivers/linux-2.6''?  (I forget what name we 
> settled on for the generic VT/Pacifica abstraction, I think 
> it was ''hve''.)
>From my recollection, it''s hvm. 
--
Mats
> 
> Ian
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 

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

> This patch adds a directory for para-driver support in 
> unmodified linux.
> The event channel is made to a pci device, the event is 
> delivered by this device.
> The build script will create the symbol link to linux-sparse 
> tree for all the front end driver. A prinstine kernel path 
> shall be given in compile.sh.
Does this follow ''best practice'' for building out of tree
linux kernel
modules? Or at least copy the build practice for other common modules?

I don''t think its really a sparse tree, so we should probably change
the
name.
Perhaps ''hve-drivers/linux-2.6''?  (I forget what name we
settled on for
the generic VT/Pacifica abstraction, I think it was ''hve''.)

Ian

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

Ian Pratt wrote:
>>This patch adds a directory for para-driver support in 
>>unmodified linux.
>>The event channel is made to a pci device, the event is 
>>delivered by this device.
>>The build script will create the symbol link to linux-sparse 
>>tree for all the front end driver. A prinstine kernel path 
>>shall be given in compile.sh.
> 
> 
> Does this follow ''best practice'' for building out of tree
linux kernel
> modules? Or at least copy the build practice for other common modules?
I think it follows Documents/kbuild/modules.txt
some CFLAGS are come from xenlinux like NOSTDINC_FLAGS
> I don''t think its really a sparse tree, so we should probably
change the
> name.
> Perhaps ''hve-drivers/linux-2.6''?  (I forget what name we
settled on for
> the generic VT/Pacifica abstraction, I think it was
''hve''.)
Yes, The sparse just mean to driver/xen/, not linux.
so maybe hvm-drivers/linux-2.6 is better.


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