From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 2/3] virtio-pci: Use ioeventfd for virtqueue notify Date: Thu, 11 Nov 2010 18:59:29 +0200 Message-ID: <4CDC20F1.1030305@redhat.com> References: <1289483242-6069-1-git-send-email-stefanha@linux.vnet.ibm.com> <1289483242-6069-3-git-send-email-stefanha@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, "Michael S. Tsirkin" To: Stefan Hajnoczi Return-path: Received: from mx1.redhat.com ([209.132.183.28]:42543 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754405Ab0KKQ7j (ORCPT ); Thu, 11 Nov 2010 11:59:39 -0500 In-Reply-To: <1289483242-6069-3-git-send-email-stefanha@linux.vnet.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: On 11/11/2010 03:47 PM, Stefan Hajnoczi wrote: > Some virtio devices are known to have guest drivers which expect a notify to be > processed synchronously and spin waiting for completion. Only enable ioeventfd > for virtio-blk and virtio-net for now. Which drivers are these? I only know of the virtio-gl driver, which isn't upstream. -- error compiling committee.c: too many arguments to function