From: Avi Kivity <avi@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] exec.c: Fix subpage memory access to RAM MemoryRegion
Date: Tue, 29 Nov 2011 18:46:43 +0200 [thread overview]
Message-ID: <4ED50C73.8090507@redhat.com> (raw)
In-Reply-To: <4ED505FE.2090808@suse.de>
On 11/29/2011 06:19 PM, Andreas Färber wrote:
> Am 29.11.2011 15:00, schrieb Avi Kivity:
> > On 11/29/2011 02:47 PM, Andreas Färber wrote:
> >>>
> >>> addr += mmio->region_offset[idx];
> >>> idx = mmio->sub_io_index[idx];
> >>> + if (unlikely(idx == IO_MEM_RAM)) {
> >>> + ram_addr_t raddr = /*mmio->base |*/ addr;
> >>> + void *ptr = qemu_get_ram_ptr(raddr);
> >>
> >> ...and/or this seems to lead to "Bad RAM pointer" (or so) when there's
> >> ELF code loaded into the subpage at that address despite being IO_MEM_RAM?
> >> (Seen, e.g., if for RL78 I increase the page size from 12 to 16.)
> >>
> >
> > addr is relative to the start of the page, instead of the start of the
> > region. You can use mmio->region_offset[idx] to compensate.
>
> That's exactly what the first line of the snippet above does, no?
> (sorry, there's still a confusing comment from an earlier attempt)
>
Depends on whether ->region_offset has the right value or not, where's
the code that adjusts it? For your case that does f00-fff it should be
-0xf00 + ram_addr (of the start of the region).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-11-29 16:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 15:06 [Qemu-devel] [PATCH] exec.c: Fix subpage memory access to RAM MemoryRegion Andreas Färber
2011-11-28 17:17 ` Avi Kivity
2011-11-28 22:39 ` Andreas Färber
2011-11-29 9:52 ` Avi Kivity
2011-11-30 15:34 ` Andreas Färber
2011-11-29 12:47 ` Andreas Färber
2011-11-29 14:00 ` Avi Kivity
2011-11-29 16:19 ` Andreas Färber
2011-11-29 16:46 ` Avi Kivity [this message]
2011-11-30 16:22 ` Andreas Färber
2011-12-01 9:24 ` Avi Kivity
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=4ED50C73.8090507@redhat.com \
--to=avi@redhat.com \
--cc=afaerber@suse.de \
--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.