From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56193) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VdkBi-00068x-Px for qemu-devel@nongnu.org; Tue, 05 Nov 2013 12:13:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VdkBd-0002J3-T3 for qemu-devel@nongnu.org; Tue, 05 Nov 2013 12:13:10 -0500 Received: from mx1.redhat.com ([209.132.183.28]:52064) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VdkBd-0002Ii-LX for qemu-devel@nongnu.org; Tue, 05 Nov 2013 12:13:05 -0500 Date: Tue, 5 Nov 2013 19:16:02 +0200 From: "Michael S. Tsirkin" Message-ID: <20131105171602.GA24940@redhat.com> References: <1381848154-31602-1-git-send-email-peter.maydell@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH v2] docs/memory.txt: Clarify and expand priority/overlap documentation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: QEMU Developers , Anthony Liguori , Patch Tracking On Tue, Nov 05, 2013 at 05:11:09PM +0000, Peter Maydell wrote: > On 15 October 2013 15:42, Peter Maydell wrote: > > The documentation of how overlapping memory regions behave and how > > the priority system works was rather brief, and confusion about > > priorities seems to be quite common for developers trying to understand > > how the memory region system works, so expand and clarify it. > > This includes a worked example with overlaps, documentation of the > > behaviour when an overlapped container has "holes", and mention > > that it's valid for a region to have both MMIO callbacks and > > subregions (and how this interacts with priorities when it does). > > > > Signed-off-by: Peter Maydell > > Ping! > > thanks > -- PMM Want to fix minor typos that Eric found?