All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Riley <rileyrd@purdue.edu>
To: xen-devel@lists.xensource.com
Subject: Documentation For Writing a Split Driver
Date: Thu, 15 Feb 2007 15:33:36 -0500	[thread overview]
Message-ID: <45D4C3A0.3010908@purdue.edu> (raw)

I've spent the last few weeks digging around in Xen code and old 
documentation to produce my own simple split driver for 3.0.4-2 to 
handle some logging stuff that I'm doing.  In the process, I quickly 
discovered that the Wiki documentation for adding a new driver to Xen is 
a little lacking.  Is there any interest in me documenting any/all of 
the following and contributing it?
-Creating a backend/frontend skeleton driver and adding it to the kernel.
-Modifying xend and xm to initialize the XenStore for it.  (and hence 
get the probe functions to be called)
-Setting up event channels
-Setting up a ring buffer
-Sharing memory pages between domains (basically the grant tables)

Thanks
Ryan

             reply	other threads:[~2007-02-15 20:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 20:33 Ryan Riley [this message]
2007-02-16 14:57 ` Documentation For Writing a Split Driver Ian Pratt
2007-02-16 15:38   ` Thomas Friebel
2007-02-19 16:33 ` Mark Williamson

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=45D4C3A0.3010908@purdue.edu \
    --to=rileyrd@purdue.edu \
    --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.