From: Avi Kivity <avi@redhat.com>
To: Cam Macdonell <cam@cs.ualberta.ca>
Cc: "kvm@vger.kernel.org list" <kvm@vger.kernel.org>,
Gregory Haskins <ghaskins@novell.com>
Subject: Re: [PATCH v2] Shared memory device with interrupt support
Date: Mon, 18 May 2009 20:19:18 +0300 [thread overview]
Message-ID: <4A119896.80904@redhat.com> (raw)
In-Reply-To: <4A1191D6.6090105@cs.ualberta.ca>
Cam Macdonell wrote:
>
> My usual noob questions: Do I need to run Greg's tree on the host for
> the necessary irqfd/eventfd suppport?
Yes (though irqfd will be merged real soon, and iosignalfd somewhat
afterwards).
> Are there any examples to work from aside from Greg's unit tests?
No.
You don't really need to irqfd and iosignalfd to implement all of this,
they're just optimizations. You can still pass the eventfds around. If
you don't have irqfd, have qemu poll the eventfd, and when something
happens, inject and interrupt. Likewise, if you don't have iosignalfd,
register a pio/mmio handler for the command register, and when they fire
touch all of the relevant irqfds. You'll need that anyway for backwards
compatibility and for level-triggered pci interrupts, which irqfd
doesn't support.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-05-18 17:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D9CB4061D1EB3408D4A0B910433453C030BCA8892@inbmail01.lsi.com>
2009-05-16 3:30 ` [PATCH v2] Shared memory device with interrupt support Cam Macdonell
2009-05-17 21:51 ` Avi Kivity
2009-05-18 11:12 ` Gregory Haskins
2009-05-18 11:38 ` Avi Kivity
2009-05-18 16:50 ` Cam Macdonell
2009-05-18 17:19 ` Avi Kivity [this message]
2009-05-18 12:11 ` Kumar, Venkat
2009-05-18 16:20 ` Cam Macdonell
2009-05-19 3:52 ` Kumar, Venkat
2009-05-19 11:20 ` Jayaraman, Bhaskar
2009-05-19 11:35 ` Gregory Haskins
2009-05-07 16:16 Cam Macdonell
2009-05-16 2:45 ` Kumar, Venkat
2009-05-16 3:27 ` Cam Macdonell
2009-05-17 21:39 ` Avi Kivity
2009-05-18 18:54 ` Anthony Liguori
2009-05-19 4:31 ` Avi Kivity
2009-05-19 18:31 ` Anthony Liguori
2009-05-20 9:01 ` Avi Kivity
2009-05-20 13:45 ` Anthony Liguori
2009-05-20 14:26 ` 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=4A119896.80904@redhat.com \
--to=avi@redhat.com \
--cc=cam@cs.ualberta.ca \
--cc=ghaskins@novell.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 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.