From: NAHieu <nahieu@gmail.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Do I need xenbus_driver?
Date: Thu, 29 Sep 2005 13:41:20 +0900 [thread overview]
Message-ID: <5d7aca950509282141370c31bd@mail.gmail.com> (raw)
Hi,
I am writing a small kernel module, which splits into 2 part: one runs
in dom0, and the other runs in domU. The main job is to exchange some
data between them, and there is no hardware related.
It seems simple enough: dom0 module watches for domU via xenstore,
then they exchange grant-table-ref with each other and then go ahead
doing their work.
The problem is: I saw all the xen drivers, and they all register to
xenbus (with xenbus_driver structure). Look again at my code, I dont
see why I need to exploit the xebus_driver interface. So my question
is: Why I need xenbus_driver in my case, and what is the advantages?
(That confuses me is looks like I can survive without it)
Many thanks.
Hieu
reply other threads:[~2005-09-29 4:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5d7aca950509282141370c31bd@mail.gmail.com \
--to=nahieu@gmail.com \
--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.