From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
Michael Tokarev <mjt@tls.msk.ru>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] [PATCH v2 2/2] docs/memory.txt: Fix document on MMIO operations
Date: Mon, 5 May 2014 18:59:51 +0800 [thread overview]
Message-ID: <1399287591-6525-3-git-send-email-famz@redhat.com> (raw)
In-Reply-To: <1399287591-6525-1-git-send-email-famz@redhat.com>
.impl.valid should be .impl.unaligned and the description needs some
fixes.
Signed-off-by: Fam Zheng <famz@redhat.com>
---
docs/memory.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/docs/memory.txt b/docs/memory.txt
index d5abc92..4c7bc43 100644
--- a/docs/memory.txt
+++ b/docs/memory.txt
@@ -232,7 +232,8 @@ various constraints can be supplied to control how these callbacks are called:
(in bytes) supported by the *implementation*; other access sizes will be
emulated using the ones available. For example a 4-byte write will be
emulated using four 1-byte writes, if .impl.max_access_size = 1.
- - .impl.valid specifies that the *implementation* only supports unaligned
- accesses; unaligned accesses will be emulated by two aligned accesses.
+ - .impl.unaligned specifies that the *implementation* supports unaligned
+ accesses; if false, an unaligned access will be emulated by two aligned
+ accesses.
- .old_mmio can be used to ease porting from code using
cpu_register_io_memory(). It should not be used in new code.
--
1.9.2
next prev parent reply other threads:[~2014-05-05 11:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 10:59 [Qemu-devel] [PATCH v2 0/2] docs/memory.txt: Fixes on whitespace and MMIO operations Fam Zheng
2014-05-05 10:59 ` [Qemu-devel] [PATCH v2 1/2] docs/memory.txt: Put one whitespace between sentences Fam Zheng
2014-05-05 11:05 ` Michael Tokarev
2014-05-05 11:30 ` Fam Zheng
2014-05-05 10:59 ` Fam Zheng [this message]
2014-05-05 11:05 ` [Qemu-devel] [PATCH v2 0/2] docs/memory.txt: Fixes on whitespace and MMIO operations Fam Zheng
2014-05-05 11:07 ` Michael Tokarev
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=1399287591-6525-3-git-send-email-famz@redhat.com \
--to=famz@redhat.com \
--cc=mjt@tls.msk.ru \
--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).