From: hitmoon <zxq_yx_007@163.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] doc/memory.txt: correct a logic error
Date: Fri, 26 Feb 2016 18:36:16 +0800 [thread overview]
Message-ID: <56D02AA0.70301@163.com> (raw)
In-Reply-To: <CAFEAcA8+1T3avTUMepSaAFHNNTQ0Sd2yhVtcqotgSo+3U9VztA@mail.gmail.com>
在 2016年02月26日 18:25, Peter Maydell 写道:
> On 26 February 2016 at 08:40, xiaoqiang zhao <zxq_yx_007@163.com> wrote:
>> In the regions overlap example, region B has a higher priority thus
>> should has a larger priority number than C.
>>
>> Signed-off-by: xiaoqiang zhao <zxq_yx_007@163.com>
>> ---
>> docs/memory.txt | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/docs/memory.txt b/docs/memory.txt
>> index 8745f76..d0aca05 100644
>> --- a/docs/memory.txt
>> +++ b/docs/memory.txt
>> @@ -180,8 +180,8 @@ aliases that leave holes then the lower priority region will appear in these
>> holes too.)
>>
>> For example, suppose we have a container A of size 0x8000 with two subregions
>> -B and C. B is a container mapped at 0x2000, size 0x4000, priority 1; C is
>> -an MMIO region mapped at 0x0, size 0x6000, priority 2. B currently has two
>> +B and C. B is a container mapped at 0x2000, size 0x4000, priority 2; C is
>> +an MMIO region mapped at 0x0, size 0x6000, priority 1. B currently has two
>> of its own subregions: D of size 0x1000 at offset 0 and E of size 0x1000 at
>> offset 0x2000. As a diagram:
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
>
> I suspect I was thinking of other systems where lower numbers are higher
> priorities...
>
> thanks
> -- PMM
Well, it's not consistency.
next prev parent reply other threads:[~2016-02-26 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 8:40 [Qemu-devel] [PATCH] doc/memory.txt: correct a logic error xiaoqiang zhao
2016-02-26 10:25 ` Peter Maydell
2016-02-26 10:36 ` hitmoon [this message]
2016-03-03 14:39 ` Paolo Bonzini
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=56D02AA0.70301@163.com \
--to=zxq_yx_007@163.com \
--cc=pbonzini@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).