From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] doc/memory.txt: fix typo
Date: Fri, 26 Feb 2016 10:36:00 +0800 [thread overview]
Message-ID: <56CFBA10.7000708@cn.fujitsu.com> (raw)
In-Reply-To: <CAFEAcA9=u6FiqNTw25x3k5uLKZ9QnDqsho2BdfqZ-ybjfRa_fA@mail.gmail.com>
On 02/25/2016 10:24 PM, Peter Maydell wrote:
> On 25 February 2016 at 13:30, Cao jin <caoj.fnst@cn.fujitsu.com> wrote:
>
> You're certainly right that the documentation as it stands is wrong.
> I don't think this is a simple typo though. Probably what happened
> was that when the API was being designed it started off with an
> 'unaligned' field, and then later the field name and semantics
> were changed but the docs weren't updated to match. My point was
> that just changing the name without looking at the behaviour we're
> actually implementing isn't correct.
>
Totally agree with the point.
>> I admit that, the description like ".valid.unaligned specifies that the
>> device only accepts naturally aligned accesses" looks very confusing. But
>> from the only caller memory_region_access_valid(), I think the original
>> maybe not quite good? how about this:
>
>> /.valid.unaligned specifies that the device accepts unaligned accesses. If
>> false, Unaligned accesses invoke device and bus specific behaviour/
>
> I would suggest:
>
> - .valid.unaligned specifies that the *device being modelled*
> supports unaligned accesses; if false, unaligned accesses will
> invoke the appropriate bus or CPU specific behaviour.
>
Does better. I want to pack this into a trivial patch first, because the
original is not easy to read & understand
> (the idea being to make the text parallel to the existing
> .impl.unaligned docs so it's clear what the difference is.)
>
> thanks
> -- PMM
>
>
> .
>
--
Yours Sincerely,
Cao jin
next prev parent reply other threads:[~2016-02-26 2:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 9:32 [Qemu-devel] [PATCH] doc/memory.txt: fix typo Cao jin
2016-02-25 10:00 ` Peter Maydell
2016-02-25 10:05 ` Cao jin
2016-02-25 13:30 ` Cao jin
2016-02-25 14:24 ` Peter Maydell
2016-02-26 2:36 ` Cao jin [this message]
2016-03-03 14:45 ` Paolo Bonzini
2016-03-03 14:54 ` 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=56CFBA10.7000708@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=pbonzini@redhat.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 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).