From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xiaofeng Ling Subject: Re: [PATCH][VT] add a directory for para-driver support in unmodified linux. Date: Mon, 05 Sep 2005 16:30:20 +0800 Message-ID: <431C021C.3050300@intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: xen-devel List-Id: xen-devel@lists.xenproject.org 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.