All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiaofeng Ling <xiaofeng.ling@intel.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH][VT] add a directory for para-driver support in unmodified linux.
Date: Mon, 05 Sep 2005 16:30:20 +0800	[thread overview]
Message-ID: <431C021C.3050300@intel.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282E59@liverpoolst.ad.cl.cam.ac.uk>

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.

  reply	other threads:[~2005-09-05  8:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-05  8:02 [PATCH][VT] add a directory for para-driver support in unmodified linux Ian Pratt
2005-09-05  8:30 ` Xiaofeng Ling [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-05  4:45 Xiaofeng Ling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=431C021C.3050300@intel.com \
    --to=xiaofeng.ling@intel.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.