From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH v2] doc/memory.txt: fix typo
Date: Fri, 26 Feb 2016 19:12:58 +0800 [thread overview]
Message-ID: <56D0333A.2000605@cn.fujitsu.com> (raw)
In-Reply-To: <CAFEAcA8+ekWvpkch2-YrOVdyVOjtH2t3R851WEj4k49DGCd-2Q@mail.gmail.com>
On 02/26/2016 07:03 PM, Peter Maydell wrote:
> On 26 February 2016 at 10:59, Cao jin <caoj.fnst@cn.fujitsu.com> wrote:
>>
>> diff --git a/docs/memory.txt b/docs/memory.txt
>> index 8745f76..8aee3d6 100644
>> --- a/docs/memory.txt
>> +++ b/docs/memory.txt
>> @@ -186,15 +186,15 @@ of its own subregions: D of size 0x1000 at offset 0 and E of size 0x1000 at
>> offset 0x2000. As a diagram:
>>
>> 0 1000 2000 3000 4000 5000 6000 7000 8000
>> - |------|------|------|------|------|------|------|-------|
>> + |------|------|------|------|------|------|------|------|
>> A: [ ]
>> - C: [CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC]
>> - B: [ ]
>> - D: [DDDDD]
>> - E: [EEEEE]
>> + C: [CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC]
>> + B: [ ]
>> + D: [DDDDDD]
>> + E: [EEEEEE]
>>
>> The regions that will be seen within this address range then are:
>> - [CCCCCCCCCCCC][DDDDD][CCCCC][EEEEE][CCCCC]
>> + [CCCCCCCCCCCCC[DDDDDD]CCCCCC[EEEEEE]CCCCCC]
>>
>> Since B has higher priority than C, its subregions appear in the flat map
>> even where they overlap with C. In ranges where B has not mapped anything
>> @@ -203,7 +203,7 @@ C's region appears.
>> If B had provided its own MMIO operations (ie it was not a pure container)
>> then these would be used for any addresses in its range not handled by
>> D or E, and the result would be:
>> - [CCCCCCCCCCCC][DDDDD][BBBBB][EEEEE][BBBBB]
>> + [CCCCCCCCCCCCC[DDDDDD]BBBBBB[EEEEEE]BBBBBB]
>>
>> Priority values are local to a container, because the priorities of two
>> regions are only compared when they are both children of the same container.
>
> Why is this patch touching all these ascii art diagrams? If you want
> to change them, that's a different patch, but I don't see any need to.
> In fact you seem to have lost some of the [] from your version, so your
> change doesn't look like an improvement to me.
>
well, the diagram seem not aligned so well, so I did the modification.
>
> thanks
> -- PMM
>
>
> .
>
--
Yours Sincerely,
Cao jin
WARNING: multiple messages have this Message-ID (diff)
From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] doc/memory.txt: fix typo
Date: Fri, 26 Feb 2016 19:12:58 +0800 [thread overview]
Message-ID: <56D0333A.2000605@cn.fujitsu.com> (raw)
In-Reply-To: <CAFEAcA8+ekWvpkch2-YrOVdyVOjtH2t3R851WEj4k49DGCd-2Q@mail.gmail.com>
On 02/26/2016 07:03 PM, Peter Maydell wrote:
> On 26 February 2016 at 10:59, Cao jin <caoj.fnst@cn.fujitsu.com> wrote:
>>
>> diff --git a/docs/memory.txt b/docs/memory.txt
>> index 8745f76..8aee3d6 100644
>> --- a/docs/memory.txt
>> +++ b/docs/memory.txt
>> @@ -186,15 +186,15 @@ of its own subregions: D of size 0x1000 at offset 0 and E of size 0x1000 at
>> offset 0x2000. As a diagram:
>>
>> 0 1000 2000 3000 4000 5000 6000 7000 8000
>> - |------|------|------|------|------|------|------|-------|
>> + |------|------|------|------|------|------|------|------|
>> A: [ ]
>> - C: [CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC]
>> - B: [ ]
>> - D: [DDDDD]
>> - E: [EEEEE]
>> + C: [CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC]
>> + B: [ ]
>> + D: [DDDDDD]
>> + E: [EEEEEE]
>>
>> The regions that will be seen within this address range then are:
>> - [CCCCCCCCCCCC][DDDDD][CCCCC][EEEEE][CCCCC]
>> + [CCCCCCCCCCCCC[DDDDDD]CCCCCC[EEEEEE]CCCCCC]
>>
>> Since B has higher priority than C, its subregions appear in the flat map
>> even where they overlap with C. In ranges where B has not mapped anything
>> @@ -203,7 +203,7 @@ C's region appears.
>> If B had provided its own MMIO operations (ie it was not a pure container)
>> then these would be used for any addresses in its range not handled by
>> D or E, and the result would be:
>> - [CCCCCCCCCCCC][DDDDD][BBBBB][EEEEE][BBBBB]
>> + [CCCCCCCCCCCCC[DDDDDD]BBBBBB[EEEEEE]BBBBBB]
>>
>> Priority values are local to a container, because the priorities of two
>> regions are only compared when they are both children of the same container.
>
> Why is this patch touching all these ascii art diagrams? If you want
> to change them, that's a different patch, but I don't see any need to.
> In fact you seem to have lost some of the [] from your version, so your
> change doesn't look like an improvement to me.
>
well, the diagram seem not aligned so well, so I did the modification.
>
> thanks
> -- PMM
>
>
> .
>
--
Yours Sincerely,
Cao jin
next prev parent reply other threads:[~2016-02-26 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 10:59 [Qemu-trivial] [PATCH v2] doc/memory.txt: fix typo Cao jin
2016-02-26 10:59 ` [Qemu-devel] " Cao jin
2016-02-26 11:03 ` [Qemu-trivial] " Peter Maydell
2016-02-26 11:03 ` Peter Maydell
2016-02-26 11:12 ` Cao jin [this message]
2016-02-26 11:12 ` Cao jin
2016-02-26 11:17 ` [Qemu-trivial] " Peter Maydell
2016-02-26 11:17 ` 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=56D0333A.2000605@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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.