From: mk.xen-devel@simplecheck.net
To: rileyrd@gmail.com
Cc: xen-devel@lists.xensource.com
Subject: Re: DomU-Dom0 communication question
Date: Wed, 02 May 2007 15:06:09 -0400 [thread overview]
Message-ID: <31835741.705661178132769762.JavaMail.servlet@perfora> (raw)
On 5/2/07, Ryan Riley <rileyrd@gmail.com> wrote:
> > 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.
> >
>
> Hmm, it sounds like you may be a bit confused regarding how the split
> drivers work.
Yes, I am :-)
> For any useful frontend/backend device each side ends up
> being two drivers in one. One is the frontend/backend driver, the other is
> the device that the OS sees. For example, the networking frontend has all
> of the code the being a Xen frontend driver (event channels, probe handling,
> etc) and is also a network device that the guest interacts with. In a sense
> it registers itself as two drivers.
That is the driver I was going through to get an idea how it works. I see the network adapter registration part, but since I am not familiar with network drivers APIs I got confused what exactly is going on.
> You could definitely write a split driver that has character devices on both
> ends that share data. My backend driver for the project I mentioned above
> is exactly that. (Frontend kernel puts data onto a ring buffer, backend
> kernel reads it off and makes it available as a character device.)
Sounds exactly what I need, except I was thinking to have messages in both directions.
> This probably sounds bad, but if you can get away with it I would do
> everything is user space and send your arbitrary data/buffers over the
> network link. Trust me when I say that you'll lose less hair that way.
I think, the split drivers give me a better control for the task I am doing. I do not want to rely on network being setup correctly.
> If you decide to go the split driver route, I can supply you with my code.
> It isn't pretty, but it may help you out. Let me know if you're interested.
I am definitely interested! I was out of writing Linux drivers for quite some time and I appreciate any help I can get.
Thanks.
Max
next reply other threads:[~2007-05-02 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 19:06 mk.xen-devel [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-02 14:26 DomU-Dom0 communication question mk.xen-devel
2007-05-02 16:04 ` Ryan Riley
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=31835741.705661178132769762.JavaMail.servlet@perfora \
--to=mk.xen-devel@simplecheck.net \
--cc=rileyrd@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.