From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] ROM write access for debugging
Date: Sat, 28 Mar 2009 12:51:54 -0500 [thread overview]
Message-ID: <49CE63BA.3060303@us.ibm.com> (raw)
In-Reply-To: <49BFDB53.9020004@siemens.com>
Jan Kiszka wrote:
> Enhance cpu_memory_rw_debug so that it can write even to ROM regions.
> This allows to modify ROM via gdb (I see no point in denying this to the
> user), and it will enable us to drop kvm_patch_opcode_byte().
>
> Credits go to Avi for suggesting this.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>
Applied both in series. Thanks.
Regards,
Anthony Liguori
> ---
>
> exec.c | 11 ++++++++---
> 1 files changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/exec.c b/exec.c
> index 86ab7de..5e94a8f 100644
> --- a/exec.c
> +++ b/exec.c
> @@ -3448,7 +3448,7 @@ void stq_phys(target_phys_addr_t addr, uint64_t val)
>
> #endif
>
> -/* virtual memory access for debug */
> +/* virtual memory access for debug (includes writing to ROM) */
> int cpu_memory_rw_debug(CPUState *env, target_ulong addr,
> uint8_t *buf, int len, int is_write)
> {
> @@ -3465,8 +3465,13 @@ int cpu_memory_rw_debug(CPUState *env, target_ulong addr,
> l = (page + TARGET_PAGE_SIZE) - addr;
> if (l > len)
> l = len;
> - cpu_physical_memory_rw(phys_addr + (addr & ~TARGET_PAGE_MASK),
> - buf, l, is_write);
> + phys_addr += (addr & ~TARGET_PAGE_MASK);
> +#if !defined(CONFIG_USER_ONLY)
> + if (is_write)
> + cpu_physical_memory_write_rom(phys_addr, buf, l);
> + else
> +#endif
> + cpu_physical_memory_rw(phys_addr, buf, l, is_write);
> len -= l;
> buf += l;
> addr += l;
>
>
>
>
prev parent reply other threads:[~2009-03-28 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 17:18 [Qemu-devel] [PATCH 1/2] ROM write access for debugging Jan Kiszka
2009-03-28 17:51 ` Anthony Liguori [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=49CE63BA.3060303@us.ibm.com \
--to=aliguori@us.ibm.com \
--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).