From: Anthony Liguori <anthony@codemonkey.ws>
To: Cam Macdonell <cam@cs.ualberta.ca>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] VirtIO Support for Memory Regions
Date: Tue, 23 Feb 2010 15:09:08 -0600 [thread overview]
Message-ID: <4B8443F4.6080903@codemonkey.ws> (raw)
In-Reply-To: <4B84432C.6090104@codemonkey.ws>
On 02/23/2010 03:05 PM, Anthony Liguori wrote:
> Hi Cam,
>
> On 02/23/2010 02:52 PM, Cam Macdonell wrote:
>> Support for passing memory regions via VirtIO to remove need for PCI
>> support in the guest.
>>
>> Adds new vectors to VirtIO config space to pass memory regions similar
>> to how virtqueues are passed.
>>
>> Kernel patch is forthcoming that add device_ops to access the memory
>> regions.
>>
>> I have used this mechanism to implement my host shared memory
>> implementation
>> and modified Alex's Virtio FB to use it as well.
>
> Virtio is really a DMA engine. One of the nice things about it's
> design is that you can do things like transparent bounce buffering if
> needed. Adding a mechanism like this breaks this abstract and turns
> virtio into something that's more than I think it should be.
More specifically, virtio does not assume cache coherent shared memory
today. While we assume this in the virtio-pci vring implementation,
that's just an implementation detail of one transport. Adding generic
shared memory to virtio presumes that one can have cache coherent shared
memory in any virtio transport which is not a good assumption to make.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-02-23 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 20:52 [Qemu-devel] [PATCH] VirtIO Support for Memory Regions Cam Macdonell
2010-02-23 21:05 ` Anthony Liguori
2010-02-23 21:09 ` Anthony Liguori [this message]
2010-02-24 6:20 ` Cam Macdonell
2010-02-24 11:14 ` Avi Kivity
2010-02-24 15:01 ` Anthony Liguori
2010-02-24 15:13 ` Anthony Liguori
2010-02-24 15:41 ` Anthony Liguori
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=4B8443F4.6080903@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=cam@cs.ualberta.ca \
--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).