From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 2/3] memory: add API for creating ROM/device regions
Date: Fri, 12 Aug 2011 08:48:24 -0500 [thread overview]
Message-ID: <4E452F28.5000902@codemonkey.ws> (raw)
In-Reply-To: <1312822730-9577-3-git-send-email-avi@redhat.com>
On 08/08/2011 11:58 AM, Avi Kivity wrote:
> ROM/device regions act as mapped RAM for reads, can I/O memory for
> writes. This allow emulation of flash devices.
>
> Signed-off-by: Avi Kivity<avi@redhat.com>
> ---
> memory.c | 46 ++++++++++++++++++++++++++++++++++++++++++++--
> memory.h | 34 ++++++++++++++++++++++++++++++++++
> 2 files changed, 78 insertions(+), 2 deletions(-)
>
> diff --git a/memory.c b/memory.c
> index 5e3d966..beff98c 100644
> --- a/memory.c
> +++ b/memory.c
> @@ -125,6 +125,7 @@ struct FlatRange {
> target_phys_addr_t offset_in_region;
> AddrRange addr;
> uint8_t dirty_log_mask;
> + bool readable;
In a follow up, it might be good to add a comment explaining that this
whole readable thing is not just an optimization, but a hard requirement
for KVM in order to be able to execute code from ROM.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2011-08-12 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 16:58 [Qemu-devel] [PATCH 0/3] Memory API updates Avi Kivity
2011-08-08 16:58 ` [Qemu-devel] [PATCH 1/3] memory: reclaim resources when a memory region is destroyed for good Avi Kivity
2011-08-08 16:58 ` [Qemu-devel] [PATCH 2/3] memory: add API for creating ROM/device regions Avi Kivity
2011-08-12 13:48 ` Anthony Liguori [this message]
2011-08-14 3:05 ` Avi Kivity
2011-08-14 13:29 ` Anthony Liguori
2011-08-14 15:43 ` Alexander Graf
2011-08-14 13:51 ` Anthony Liguori
2011-08-08 16:58 ` [Qemu-devel] [PATCH 3/3] memory: correct documentation typos Avi Kivity
2011-08-12 13:47 ` [Qemu-devel] [PATCH 0/3] Memory API updates Anthony Liguori
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=4E452F28.5000902@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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).