From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [KVM PATCH v8 3/3] KVM: add iosignalfd support Date: Mon, 22 Jun 2009 14:26:50 +0200 Message-ID: <4A3F788A.9000007@redhat.com> References: <20090619002224.15859.97977.stgit@dev.haskins.net> <20090619003045.15859.73197.stgit@dev.haskins.net> <20090622104435.GA11594@redhat.com> <4A3F757C.6030508@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Michael S. Tsirkin" , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, avi@redhat.com, mtosatti@redhat.com, paulmck@linux.vnet.ibm.com, markmc@redhat.com To: Gregory Haskins Return-path: In-Reply-To: <4A3F757C.6030508@novell.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org >>> + * Design note: We create one PIO/MMIO device (iosignalfd_group) which >>> + * aggregates one or more iosignalfd_items. Each item points to exactly one >>> + * eventfd, and can be registered to trigger on any write to the group >>> + * (wildcard), or to a write of a specific value. If more than one item is to >>> + * be supported, the addr/len ranges must all be identical in the group. If a >>> + * trigger value is to be supported on a particular item, the group range must >>> + * be exactly the width of the trigger. >>> >> Some duplicate spaces in the text above, apparently at random places. > > -ENOPARSE ;) > > Can you elaborate? I see "aggregates one". The others are all at end of sentence, so I think that Michael was not talking about those (git grep '\*.*\. '). Paolo