qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <andreas.faerber@web.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Initializing PC from memory on reset?
Date: Thu, 24 Nov 2011 22:24:13 +0100	[thread overview]
Message-ID: <4ECEB5FD.6010404@web.de> (raw)
In-Reply-To: <CAFEAcA-+3o997=GMh9Y6nGSW8dfg7a3v7XXK8Zyyh-vRAzGzgg@mail.gmail.com>

Am 24.11.2011 08:47, schrieb Peter Maydell:
> On 23 November 2011 23:59, Andreas Färber <andreas.faerber@web.de> wrote:
>> Unlike PowerPC, an architecture that I'm trying to emulate does not
>> store branch instructions in the reset vector but a memory address. I'm
>> therefore trying to read physical address 0x00000 and store its value
>> into my env->pc.
> 
> Have you looked at how M profile ARM does it? That has a similar
> "read memory for initial PC value". (There are some interesting
> wrinkles, not all of which we get quite right, regarding how this
> should interact with initial ELF image load and the user fiddling
> with PC and RAM in an attached debugger.)

Thanks. I thought I had seen something like that but apparently grep'ed
for the wrong keywords.

Can anyone enlighten me why rom_ptr()+lduw_p() works at this point in
time and lduw_phys() doesn't but later does? The MemoryRegion is
initialized as a ram area. Is this a legacy issue (pre-Memory API)?

Andreas

  reply	other threads:[~2011-11-24 21:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 23:59 [Qemu-devel] Initializing PC from memory on reset? Andreas Färber
2011-11-24  7:47 ` Peter Maydell
2011-11-24 21:24   ` Andreas Färber [this message]
2011-11-25 16:25 ` [Qemu-devel] Memory read/write issues (was: Initializing PC from memory on reset?) Andreas Färber
2011-11-27  8:32   ` [Qemu-devel] Memory read/write issues Avi Kivity
2011-11-27 14:07     ` Andreas Färber
2011-11-27 14:17       ` Avi Kivity
2011-11-27 22:16         ` Andreas Färber

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=4ECEB5FD.6010404@web.de \
    --to=andreas.faerber@web.de \
    --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 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).