From: Anthony Liguori <anthony@codemonkey.ws>
To: Javier Guerra <javier@guerrag.com>
Cc: Matt Anger <angermcs@gmail.com>, kvm@vger.kernel.org
Subject: Re: Event channels in KVM?
Date: Fri, 19 Sep 2008 14:14:13 -0500 [thread overview]
Message-ID: <48D3FA05.7000101@codemonkey.ws> (raw)
In-Reply-To: <90eb1dc70809191210s6a10ce17ke1dc8663169f037a@mail.gmail.com>
Javier Guerra wrote:
> On Fri, Sep 19, 2008 at 1:31 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
>
>> Matt Anger wrote:
>>
>>> Does KVM have any interface similar to event-channels like Xen does?
>>> Basically a way to send notifications between the host and guest.
>>>
>>>
>> virtio is the abstraction we use.
>>
>> But virtio is based on the standard hardware interfaces of the PC--PIO,
>> MMIO, and interrupts.
>>
>
> this is rather low-level, it would be nice to have a multiplatform
> interface to this abstraction.
>
That's exactly the purpose of virtio. virtio is a high-level, cross
platform interface. It's been tested on x86, PPC, s390, and I believe
ia64. It also works in lguest.
It happens to use PIO, MMIO, and interrupts on x86 under KVM but other
virtio implementations exist for other platforms.
> just for kicks, i've found and printed Rusty's paper about it. hope
> it's current :-)
>
The other good thing to look at is the lguest documentation. You can
skip to just the virtio bits if you're so inclined. It's really quite
thoroughly documented.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-09-19 19:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 17:16 Event channels in KVM? Matt Anger
2008-09-19 18:31 ` Anthony Liguori
2008-09-19 19:10 ` Javier Guerra
2008-09-19 19:14 ` Anthony Liguori [this message]
2008-09-22 23:50 ` Matt Anger
2008-09-23 0:30 ` Dong, Eddie
2008-09-23 0:36 ` Matt Anger
2008-09-23 1:36 ` Dong, Eddie
2008-09-23 7:26 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2009-04-28 16:39 Kapadia, Vivek
2009-04-28 16:59 ` Anthony Liguori
2009-04-30 9:04 ` Avi Kivity
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=48D3FA05.7000101@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=angermcs@gmail.com \
--cc=javier@guerrag.com \
--cc=kvm@vger.kernel.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