From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NvqQR-0005eD-0g for qemu-devel@nongnu.org; Sun, 28 Mar 2010 07:13:03 -0400 Received: from [140.186.70.92] (port=57362 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NvqQP-0005dl-BS for qemu-devel@nongnu.org; Sun, 28 Mar 2010 07:13:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NvqQO-0005bk-2j for qemu-devel@nongnu.org; Sun, 28 Mar 2010 07:13:01 -0400 Received: from mx1.redhat.com ([209.132.183.28]:44502) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NvqQN-0005bg-S9 for qemu-devel@nongnu.org; Sun, 28 Mar 2010 07:13:00 -0400 Message-ID: <4BAF39B7.1010508@redhat.com> Date: Sun, 28 Mar 2010 14:12:55 +0300 From: Avi Kivity MIME-Version: 1.0 References: <1269497376-21903-1-git-send-email-cam@cs.ualberta.ca> <4BAB30EE.4020509@redhat.com> <8286e4ee1003250924q7cca5e71u8b8b7c6d8b785eb8@mail.gmail.com> <4BAB90BB.5030401@redhat.com> <8286e4ee1003260914u5e6ceee2pf0c00590de182fb6@mail.gmail.com> <4BAE44F2.20801@redhat.com> <20100328074754.GA21749@redhat.com> <4BAF0D03.7060300@redhat.com> <20100328094006.GB21749@redhat.com> <4BAF251E.50609@redhat.com> <20100328103123.GC21749@redhat.com> In-Reply-To: <20100328103123.GC21749@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH v3 1/1] Shared memory uio_pci driver List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Cam Macdonell , qemu-devel@nongnu.org, kvm@vger.kernel.org On 03/28/2010 01:31 PM, Michael S. Tsirkin wrote: > >> Aren't ioctls a lot simpler? >> >> Multiplexing multiple functions on write()s is just ioctls done uglier. >> > I don't have an opinion here. > > Writes do have an advantage that strace can show the buffer > content without being patched. > ioctls encode the buffer size into the ioctl number, so in theory strace doesn't need to be taught about an ioctl to show its buffer. > Further, something along the lines proposed above means that > we do not need to depend in a system header to get > the functionality. > Yes, point users at the code and let them figure out how to do stuff. -- error compiling committee.c: too many arguments to function