From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Anthony Liguori <aliguori@amazon.com>,
Patch Tracking <patches@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v2] docs/memory.txt: Clarify and expand priority/overlap documentation
Date: Tue, 5 Nov 2013 19:16:02 +0200 [thread overview]
Message-ID: <20131105171602.GA24940@redhat.com> (raw)
In-Reply-To: <CAFEAcA9AG+zsf95Kw+NFY9Qi+0mcAG+-dSMs-qFyGKdCdB5cBA@mail.gmail.com>
On Tue, Nov 05, 2013 at 05:11:09PM +0000, Peter Maydell wrote:
> On 15 October 2013 15:42, Peter Maydell <peter.maydell@linaro.org> 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 <peter.maydell@linaro.org>
>
> Ping!
>
> thanks
> -- PMM
Want to fix minor typos that Eric found?
next prev parent reply other threads:[~2013-11-05 17:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 14:42 [Qemu-devel] [PATCH v2] docs/memory.txt: Clarify and expand priority/overlap documentation Peter Maydell
2013-10-15 14:52 ` Michael S. Tsirkin
2013-10-15 14:52 ` Eric Blake
2013-10-15 14:56 ` Eric Blake
2013-10-15 14:57 ` Peter Maydell
2013-11-05 17:11 ` Peter Maydell
2013-11-05 17:16 ` Michael S. Tsirkin [this message]
2013-11-05 17:16 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131105171602.GA24940@redhat.com \
--to=mst@redhat.com \
--cc=aliguori@amazon.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.