All of lore.kernel.org
 help / color / mirror / Atom feed
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: Re: [PATCH v3 1/1] Shared memory uio_pci driver
Date: Thu, 01 Apr 2010 11:59:19 +0300	[thread overview]
Message-ID: <4BB46067.9040209@redhat.com> (raw)
In-Reply-To: <8286e4ee1003300752n41a5afdbta0b23fc0cb75b99d@mail.gmail.com>

On 03/30/2010 05:52 PM, Cam Macdonell wrote:
>
>> 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.
>>      
> Good point.  iiuc, the goal relative to ioctls in UIO was to not have
> device drivers creating their own device-specific ABIs and drivers
> that are just massive switch statements.  Having ioctls that support
> functions for UIO in general, such as pairing msi vectors to eventfds,
> does not go against that goal.
>    

Device specific ioctls are clearly a bad idea for uio.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2010-04-01  8:59 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25  6:09 [PATCH v3 1/1] Shared memory uio_pci driver Cam Macdonell
2010-03-25  9:05 ` 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: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 10:07         ` Michael S. Tsirkin
2010-03-25  9:58       ` Avi Kivity
2010-03-25  9:44     ` Michael S. Tsirkin
2010-03-25  9:40   ` Avi Kivity
2010-03-25 16:18   ` Cam Macdonell
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:50           ` Avi Kivity
2010-03-25 16:40         ` Michael S. Tsirkin
2010-03-25 16:32       ` Avi Kivity
2010-03-25 16:33       ` Michael S. Tsirkin
2010-03-25 16:33       ` Michael S. Tsirkin
2010-03-25 16:23     ` Anthony Liguori
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                       ` [Qemu-devel] " Jamie Lokier
2010-03-28 13:47                         ` malc
2010-03-28 19:48           ` Cam Macdonell
2010-03-29 20:59             ` Avi Kivity
2010-03-30 14:52               ` Cam Macdonell
2010-04-01  8:59                 ` Avi Kivity [this message]
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=4BB46067.9040209@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 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.