From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44372) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzONf-0007FB-Rm for qemu-devel@nongnu.org; Thu, 19 Nov 2015 07:32:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZzONb-00032k-O0 for qemu-devel@nongnu.org; Thu, 19 Nov 2015 07:32:03 -0500 Received: from mx1.redhat.com ([209.132.183.28]:52826) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzONb-00032W-Fz for qemu-devel@nongnu.org; Thu, 19 Nov 2015 07:31:59 -0500 References: <011b01d122af$c60f7ce0$522e76a0$@samsung.com> <20151119125348-mutt-send-email-mst@redhat.com> <014b01d122bf$ab73dc90$025b95b0$@samsung.com> <20151119135725-mutt-send-email-mst@redhat.com> <564DBB39.3010207@redhat.com> <014e01d122c4$54073d30$fc15b790$@samsung.com> From: Paolo Bonzini Message-ID: <564DC13A.2020208@redhat.com> Date: Thu, 19 Nov 2015 13:31:54 +0100 MIME-Version: 1.0 In-Reply-To: <014e01d122c4$54073d30$fc15b790$@samsung.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] virtio: Implement userspace forwarding for host notifiers List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Pavel Fedin , "'Michael S. Tsirkin'" Cc: 'Cornelia Huck' , 'Christian Borntraeger' , qemu-devel@nongnu.org On 19/11/2015 13:17, Pavel Fedin wrote: > Ok, good. So, this has already been tested. Ok, i think i can further extend this patch by: > 1. Add a flag to disable memory_region_dispatch_write_ioeventfds(), to be set by KVM code for example. So that with KVM we have even > smaller performance degradation. > 2. Issue a one-shot warning, like in my current patch, so that the user knows that his/her kernel prevents from getting the best > performance. > Will it be OK then? Yes! However QEMU pretty much always tries to use ioeventfd for virtio. I'm not sure you want to warn outside the special cases of vhost or dataplane... So perhaps it's better to warn in the vhost and dataplane case specifically, rather than always. Paolo