From: mk.xen-devel@simplecheck.net
To: xen-devel@lists.xensource.com
Subject: DomU-Dom0 communication question
Date: Wed, 02 May 2007 10:26:31 -0400 [thread overview]
Message-ID: <4591123.662921178115991050.JavaMail.servlet@perfora> (raw)
Hi all,
I need to create a custom communication channel between DomU and Dom0 in order to send arbitrary messages/buffers between applications in Dom0 and DomU.
Basically, I am thinking about making a char control driver on both sides that would transport those messages to subscribers on either end using defined IOCL calls.
I am looking at backend/frontend drivers and I don't think it would work for what I want to do as fron/back ends don't have any devices associated with it.
Would it be better to utilize event channel directly or write frontend/backend drivers and control drivers on both ends? Or maybe there is another mechanism that already exists in xen environment and I am just trying to do things the hard way? Any advise is greatly appreciated.
Thanks.
Max
next reply other threads:[~2007-05-02 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 14:26 mk.xen-devel [this message]
2007-05-02 16:04 ` DomU-Dom0 communication question Ryan Riley
-- strict thread matches above, loose matches on Subject: below --
2007-05-02 19:06 mk.xen-devel
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=4591123.662921178115991050.JavaMail.servlet@perfora \
--to=mk.xen-devel@simplecheck.net \
--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.