From: Paolo Bonzini <pbonzini@redhat.com>
To: Cao jin <caoj.fnst@cn.fujitsu.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH] doc/memory: update MMIO section
Date: Fri, 1 Apr 2016 12:47:35 +0200 [thread overview]
Message-ID: <56FE51C7.9090906@redhat.com> (raw)
In-Reply-To: <1459507677-16662-1-git-send-email-caoj.fnst@cn.fujitsu.com>
On 01/04/2016 12:47, Cao jin wrote:
> There is no memory_region_io(). And remove a stray '-'.
>
> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
> ---
> docs/memory.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/docs/memory.txt b/docs/memory.txt
> index 97134e1..fddc0d9 100644
> --- a/docs/memory.txt
> +++ b/docs/memory.txt
> @@ -37,7 +37,7 @@ MemoryRegion):
>
> - MMIO: a range of guest memory that is implemented by host callbacks;
> each read or write causes a callback to be called on the host.
> - You initialize these with memory_region_io(), passing it a MemoryRegionOps
> + You initialize these with memory_region_init_io(), passing it a MemoryRegionOps
> structure describing the callbacks.
>
> - ROM: a ROM memory region works like RAM for reads (directly accessing
> @@ -186,7 +186,7 @@ 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: [ ]
>
Queued for 2.6, thanks.
Paolo
prev parent reply other threads:[~2016-04-01 10:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 10:47 [Qemu-devel] [PATCH] doc/memory: update MMIO section Cao jin
2016-04-01 10:47 ` Paolo Bonzini [this message]
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=56FE51C7.9090906@redhat.com \
--to=pbonzini@redhat.com \
--cc=caoj.fnst@cn.fujitsu.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 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.