qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: Paul Brook <paul@codesourcery.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] sparc32 boot mode flag fix
Date: Wed, 7 Nov 2007 17:40:09 +0200	[thread overview]
Message-ID: <f43fc5580711070740w3955b4f9o2fb7ca8d95d25951@mail.gmail.com> (raw)
In-Reply-To: <200711062108.29729.paul@codesourcery.com>

On 11/6/07, Paul Brook <paul@codesourcery.com> wrote:
> > > IIUC enabling/disabling boot mode is no different to and other VM change.
> > > If the virtual->physical mapping happens to be the same then it's
> > > perfectly ok to reuse the TB.
> >
> > Not in this case: in boot mode, physical and virtual address 0
> > generates TBs from PROM code.
>
> How is this different to using the MMU to map the PROM at virtual address
> zero?

In that case, the virtual address is zero, but physical address is
0xff0000000. Oh, now I see my error, it is the same in the boot mode
case too! Sorry about the noise.

> I see exactly one use of MMU_BM. It simply hard-wires a particular
> virtual->physical address mapping.

It derives from the Sparc specification, where the PC at reset is
zero. I wonder why they didn't put the start of memory somewhere
higher instead of this hack.

On Sparc64 the reset vector is implementation dependent so it can be
directly set to the PROM address.

  reply	other threads:[~2007-11-07 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-06  2:45 [Qemu-devel] [PATCH] sparc32 boot mode flag fix Robert Reif
2007-11-06 19:31 ` Blue Swirl
2007-11-06 20:39   ` Paul Brook
2007-11-06 20:51     ` Blue Swirl
2007-11-06 21:08       ` Paul Brook
2007-11-07 15:40         ` Blue Swirl [this message]
2007-11-06 23:36   ` Robert Reif

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=f43fc5580711070740w3955b4f9o2fb7ca8d95d25951@mail.gmail.com \
    --to=blauwirbel@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).