From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH RFC] pass write value to in_range pointers Date: Tue, 23 Jun 2009 14:53:00 +0300 Message-ID: <4A40C21C.2000504@redhat.com> References: <20090619002224.15859.97977.stgit@dev.haskins.net> <20090619003045.15859.73197.stgit@dev.haskins.net> <20090622151631.GA14780@redhat.com> <4A3FA6FC.9030301@novell.com> <20090622160833.GA15228@redhat.com> <4A3FB156.3030301@novell.com> <20090622172720.GC15228@redhat.com> <4A405436.1080100@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Michael S. Tsirkin" , Gregory Haskins , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, mtosatti@redhat.com, paulmck@linux.vnet.ibm.com, markmc@redhat.com To: Gregory Haskins Return-path: Received: from mx2.redhat.com ([66.187.237.31]:44088 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752259AbZFWLwI (ORCPT ); Tue, 23 Jun 2009 07:52:08 -0400 In-Reply-To: <4A405436.1080100@gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: On 06/23/2009 07:04 AM, Gregory Haskins wrote: > Well, for one its not very clear what the benefit of the read/write > aliasing even is. ;) Apparently coalesced_mmio uses it, but even so I > doubt that is for the purposes of having one device do reads while > another does writes. I could be wrong, though. > Coalesced mmio cannot handle reads. -- error compiling committee.c: too many arguments to function