From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Gleb Natapov <gleb@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: assign-dev: Purpose of interrupt_work
Date: Mon, 12 Oct 2009 11:14:34 +0200 [thread overview]
Message-ID: <4AD2F37A.3060600@redhat.com> (raw)
In-Reply-To: <4AD2F117.7000403@web.de>
On 10/12/2009 11:04 AM, Jan Kiszka wrote:
>> I'd rather remove dev-passthrough completely than continue adding hack upon hack
>> upon hack to make is some times kinda sorta work :)
>>
> Hmm, is this code not needed for the VT-d& Co. case?
It is needed.
> Or what is the
> alternative?
>
irqfd (which only supports edge-triggered interrupts now). Note irqfd
needs the same love, it uses a workqueue as well.
The theory is:
fd1 = eventfd()
give fd1 to kvm as irqfd, vhost-net as trigger fd
fd2 = eventfd()
give fd2 to kvm as irqfd, uio as trigger fd
fd3 = evenfd()
give fd3 to kvm as irqfd, another kvm as ioeventfd
One interface, multiple users (in the kernel, userspace, or other processes)
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-10-12 9:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 7:03 assign-dev: Purpose of interrupt_work Jan Kiszka
2009-10-12 7:13 ` Gleb Natapov
2009-10-12 7:27 ` Jan Kiszka
2009-10-12 7:45 ` Gleb Natapov
2009-10-12 7:50 ` Jan Kiszka
2009-10-12 7:57 ` Gleb Natapov
2009-10-12 8:16 ` Jan Kiszka
2009-10-12 8:39 ` Gleb Natapov
2009-10-12 9:04 ` Jan Kiszka
2009-10-12 9:14 ` Avi Kivity [this message]
2009-10-12 9:25 ` Jan Kiszka
2009-10-12 9:30 ` Avi Kivity
2009-10-12 9:38 ` Gleb Natapov
2009-10-12 9:40 ` Avi Kivity
2009-10-12 9:42 ` Gleb Natapov
2009-10-12 9:14 ` Gleb Natapov
2009-10-12 8:39 ` Avi Kivity
2009-10-12 9:05 ` Gleb Natapov
2009-10-12 9:07 ` Avi Kivity
2009-10-12 9:07 ` Jan Kiszka
2009-10-12 9:16 ` Avi Kivity
2009-10-12 17:36 ` Marcelo Tosatti
2009-10-12 20:44 ` Jan Kiszka
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=4AD2F37A.3060600@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--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.