From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51107) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZUukm-0001Sh-Nm for qemu-devel@nongnu.org; Thu, 27 Aug 2015 06:49:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZUuki-0000IE-Cj for qemu-devel@nongnu.org; Thu, 27 Aug 2015 06:49:56 -0400 Received: from mail-vk0-f45.google.com ([209.85.213.45]:36542) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZUuki-0000I1-3n for qemu-devel@nongnu.org; Thu, 27 Aug 2015 06:49:52 -0400 Received: by vkif69 with SMTP id f69so7034221vki.3 for ; Thu, 27 Aug 2015 03:49:51 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <55DE970B.6040807@redhat.com> References: <1440583448-15797-1-git-send-email-jasowang@redhat.com> <20150826165140.6bab7d28@bahia.local> <55DE970B.6040807@redhat.com> From: Peter Maydell Date: Thu, 27 Aug 2015 11:49:32 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH 1/2] memory: allow zero size for adjust_endianness() List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jason Wang Cc: Paolo Bonzini , "Michael S. Tsirkin" , QEMU Developers , Greg Kurz On 27 August 2015 at 05:50, Jason Wang wrote: > On 08/26/2015 10:51 PM, Greg Kurz wrote: >> On Wed, 26 Aug 2015 15:21:59 +0100 >> Peter Maydell wrote: >>> This seems to me like a bug in the caller. Why would anything >>> try to call into the memory subsystem to do a zero-size >>> transaction? >> Here's the patch which needs zero-size eventfd: >> >> http://patchwork.ozlabs.org/patch/509428/ > Yes, this is because we want to use wildcard mmio eventfd (which > requires size to be zero) to speed up virtio 1.0 mmio. But *why* does it require the size to be zero? I still think the caller should just avoid trying to do zero-size memory operations: they don't make sense. What is a zero size operation supposed to mean? -- PMM