From: Blue Swirl <blauwirbel@gmail.com>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] device-to-device
Date: Sat, 19 Sep 2009 13:21:19 +0300 [thread overview]
Message-ID: <f43fc5580909190321i3b0f69a5v902b57294244a576@mail.gmail.com> (raw)
In-Reply-To: <20090919042617.GA24944@laped.iglesias.mooo.com>
On Sat, Sep 19, 2009 at 7:26 AM, Edgar E. Iglesias
<edgar.iglesias@gmail.com> wrote:
> Hi,
>
> Has anybody done some work on a qdev device-2-device infrastruture?
> For example to model DMA back channels or other device to device
> communication?
We should have a DMA object, with map/unmap methods to translate the
addresses to host pointers. Physical memory should implement the
object as well as any IOMMUs or other address translators like buses
(in some cases).
The interface to qdev could be much like chardev.
prev parent reply other threads:[~2009-09-19 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 4:26 [Qemu-devel] device-to-device Edgar E. Iglesias
2009-09-19 10:21 ` Blue Swirl [this message]
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=f43fc5580909190321i3b0f69a5v902b57294244a576@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=edgar.iglesias@gmail.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).