From: Avi Kivity <avi@redhat.com>
To: Cam Macdonell <cam@cs.ualberta.ca>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] Re: [PATCH v3 1/1] Shared memory uio_pci driver
Date: Mon, 29 Mar 2010 23:59:24 +0300 [thread overview]
Message-ID: <4BB114AC.9040902@redhat.com> (raw)
In-Reply-To: <8286e4ee1003281248k204a5bd4tc48e6ccc755918b@mail.gmail.com>
On 03/28/2010 10:48 PM, Cam Macdonell wrote:
> On Sat, Mar 27, 2010 at 11:48 AM, Avi Kivity<avi@redhat.com> wrote:
>
>> On 03/26/2010 07:14 PM, Cam Macdonell wrote:
>>
>>>
>>>> I'm not familiar with the uio internals, but for the interface, an
>>>> ioctl()
>>>> on the fd to assign an eventfd to an MSI vector. Similar to ioeventfd,
>>>> but
>>>> instead of mapping a doorbell to an eventfd, it maps a real MSI to an
>>>> eventfd.
>>>>
>>>>
>>> uio will never support ioctls.
>>>
>> Why not?
>>
> Perhaps I spoke too strongly, but it was rejected before
>
> http://thread.gmane.org/gmane.linux.kernel/756481
>
> With a compelling case perhaps it could be added.
>
Ah, the usual "ioctls are ugly, go away".
It could be done via sysfs:
$ cat /sys/.../msix/max-interrupts
256
$ echo 4 > /sys/.../msix/allocate
$ # subdirectories 0 1 2 3 magically appear
$ # bind fd 13 to msix
$ echo 13 > /sys/.../msix/2/bind-fd
$ # from now on, msix interrupt 2 will call eventfd_signal() on fd 13
Call me old fashioned, but I prefer ioctls.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2010-03-29 21:13 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 6:09 [Qemu-devel] [PATCH v3 1/1] Shared memory uio_pci driver Cam Macdonell
2010-03-25 9:05 ` [Qemu-devel] " Michael S. Tsirkin
2010-03-25 9:47 ` Avi Kivity
2010-03-25 16:30 ` Cam Macdonell
2010-03-25 16:34 ` Michael S. Tsirkin
2010-03-25 17:07 ` Cam Macdonell
2010-03-25 16:36 ` Avi Kivity
2010-03-25 16:37 ` Michael S. Tsirkin
2010-03-25 16:51 ` Avi Kivity
2010-03-25 9:15 ` Michael S. Tsirkin
2010-03-25 9:40 ` Avi Kivity
2010-03-25 9:44 ` Michael S. Tsirkin
2010-03-25 9:58 ` Avi Kivity
2010-03-25 10:07 ` Michael S. Tsirkin
2010-03-25 16:18 ` Cam Macdonell
2010-03-25 16:23 ` Anthony Liguori
2010-03-25 16:32 ` Avi Kivity
2010-03-25 16:40 ` Michael S. Tsirkin
2010-03-25 16:50 ` Avi Kivity
2010-03-25 16:33 ` Michael S. Tsirkin
2010-03-25 9:46 ` Avi Kivity
2010-03-25 16:24 ` Cam Macdonell
2010-03-25 16:35 ` Avi Kivity
2010-03-26 16:14 ` Cam Macdonell
2010-03-27 17:48 ` Avi Kivity
2010-03-28 7:47 ` Michael S. Tsirkin
2010-03-28 8:02 ` Avi Kivity
2010-03-28 9:40 ` Michael S. Tsirkin
2010-03-28 9:45 ` Avi Kivity
2010-03-28 10:31 ` Michael S. Tsirkin
2010-03-28 11:12 ` Avi Kivity
2010-03-28 13:28 ` Jamie Lokier
2010-03-28 13:47 ` malc
2010-03-28 19:48 ` Cam Macdonell
2010-03-29 20:59 ` Avi Kivity [this message]
2010-03-30 14:52 ` Cam Macdonell
2010-04-01 8:59 ` Avi Kivity
2010-03-31 9:12 ` Michael S. Tsirkin
2010-04-01 8:58 ` Avi Kivity
2010-04-01 10:59 ` Michael S. Tsirkin
2010-04-01 11:27 ` Avi Kivity
2010-03-25 16:42 ` Michael S. Tsirkin
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=4BB114AC.9040902@redhat.com \
--to=avi@redhat.com \
--cc=cam@cs.ualberta.ca \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--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).