From: Cam Macdonell <cam@cs.ualberta.ca>
To: Avi Kivity <avi@redhat.com>
Cc: "Christian Bornträger" <borntraeger@de.ibm.com>,
kvm@vger.kernel.org, "Rusty Russell" <rusty@rustcorp.com.au>,
"Christian Ehrhardt" <ehrhardt@linux.vnet.ibm.com>
Subject: Re: [PATCH v2] Driver for Inter-VM shared memory device for KVM supporting interrupts.
Date: Tue, 19 May 2009 10:51:08 -0600 [thread overview]
Message-ID: <4A12E37C.700@cs.ualberta.ca> (raw)
In-Reply-To: <4A127776.9030400@redhat.com>
Avi Kivity wrote:
> Christian Bornträger wrote:
>>> To summarize, Anthony thinks it should use virtio, while I believe
>>> virtio is useful for exporting guest memory, not for importing host
>>> memory.
>>>
>>
>> I think the current virtio interface is not ideal for importing host
>> memory, but we can change that. If you look at the dcssblk driver for
>> s390, it allows a guest to map shared memory segments via a diagnose
>> (hypercall). This driver uses PCI regions to map memory.
>>
>> My point is, that the method to map memory is completely irrelevant,
>> we just need something like mmap/shmget between the guest and the
>> host. We could define an interface in virtio, that can be used by any
>> transport. In case of pci this could be a simple pci map operation.
>> What do you think about something like: (CCed Rusty)
>>
>
> Exactly.
>
Agreed.
next prev parent reply other threads:[~2009-05-19 16:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 16:26 [PATCH v2] Driver for Inter-VM shared memory device for KVM supporting interrupts Cam Macdonell
2009-05-18 14:07 ` Christian Borntraeger
2009-05-18 14:26 ` Avi Kivity
2009-05-19 9:00 ` Christian Bornträger
2009-05-19 9:10 ` Avi Kivity
2009-05-19 16:51 ` Cam Macdonell [this message]
2009-05-20 2:58 ` Rusty Russell
2009-05-20 7:33 ` Christian Bornträger
2009-05-20 8:45 ` Avi Kivity
2009-05-20 9:07 ` Christian Bornträger
2009-05-20 9:11 ` Avi Kivity
2009-05-20 9:20 ` Christian Bornträger
2009-05-25 6:18 ` Rusty Russell
2009-05-20 8:07 ` François Diakhate
2009-05-19 18:39 ` Anthony Liguori
2009-05-20 7:33 ` Christian Bornträger
2009-05-20 13:26 ` Anthony Liguori
2009-05-18 16:56 ` Cam Macdonell
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=4A12E37C.700@cs.ualberta.ca \
--to=cam@cs.ualberta.ca \
--cc=avi@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=ehrhardt@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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).