From: Peter <pjcreath+openbios@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Potential sparc32 MMU bug
Date: Fri, 16 Feb 2007 13:45:57 -0500 [thread overview]
Message-ID: <d40b362a0702161045i2494888ej8d2d2cfaae2940a8@mail.gmail.com> (raw)
In-Reply-To: <200702161825.28020.paul@codesourcery.com>
Where is the policy of silently ignoring ROM writes implemented? It
may not be the proper behavior for sparc, and I'd like to tinker with
it. I'm just not sure where the write is getting suppressed (or,
alternatively, where the exception is getting suppressed).
On 2/16/07, Paul Brook <paul@codesourcery.com> wrote:
> > > I don't know about sparc, but it's normal for writes to ROM to be
> > > ignored. However by my reading the sparc bios is loaded into RAM anyway,
> > > so it shouldn't matter.
> >
> > It definitely gets blocked by something: if I leave the the trap table
> > in the .text section, the write silently fails. If I move the trap
> > table to the .data section, the write succeeds. If I move the trap
> > table over to .rodata, the write fails again. What are you looking at
> > that suggests the whole sparc bios is loaded read/write?
>
> I was mistaken. There is a ROM area defined, it's just the elf loader doesn't
> care whether it's loading to rom or ram.
>
> My comment about rom writes being silently ignored still applies.
>
> Paul
>
>
next prev parent reply other threads:[~2007-02-16 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 16:55 [Qemu-devel] Potential sparc32 MMU bug Peter
2007-02-16 17:01 ` Paul Brook
2007-02-16 18:17 ` Peter
2007-02-16 18:25 ` Paul Brook
2007-02-16 18:45 ` Peter [this message]
2007-02-16 22:50 ` Peter Creath
2007-02-17 8:21 ` Blue Swirl
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=d40b362a0702161045i2494888ej8d2d2cfaae2940a8@mail.gmail.com \
--to=pjcreath+openbios@gmail.com \
--cc=paul@codesourcery.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).