All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] sh4: define explicitly that the target CPU is 32 bit
Date: Sat, 1 Dec 2007 10:19:06 +0900	[thread overview]
Message-ID: <20071201011906.GB15027@linux-sh.org> (raw)
In-Reply-To: <200711301715.21956.paul@codesourcery.com>

On Fri, Nov 30, 2007 at 05:15:21PM +0000, Paul Brook wrote:
> On Friday 30 November 2007, Carlo Marcelo Arenas Belon wrote:
> > On Fri, Nov 30, 2007 at 04:28:09PM +0000, Paul Brook wrote:
> > in the sh4 specific case, it doesn't make sense for sh4 to print an access
> > error to a physical address that is 64 bit long when it is a 32 bit CPU and
> > that is what would happen unless the patch is applied.
> >
> > if anything the following definition from cpu-defs.h is invalid for a
> > representation of a 32 bit physical address :
> >
> > #define TARGET_FMT_plx "%016" PRIx64
> 
> Before you can fix that you probably need to fix the bits of qemu (TLB code) 
> that store a host pointer in a phys_addr_t. Or at least distance 
> TARGET_PHYS_ADDR_BITS from the definition of phys_addr_t, and include 
> appropriate comments.
> 
> In that case TARGET_PHYS_ADDR_BITS could be a precise value, rather than the 
> next multiple of 32. e.g. I think sparc32 has a 40-bit physical address 
> space.
> 
It also depends on how precise you want to make this. SH has configurable
29-bit and 32-bit physical, while MIPS and PPC both have 32 and 36-bit
physical implementations. Setting things to an arbitrary upper ceiling at
least prevents this from quickly entering ifdef hell territory.

      parent reply	other threads:[~2007-12-01  1:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 16:23 [Qemu-devel] [PATCH] sh4: define explicitly that the target CPU is 32 bit Carlo Marcelo Arenas Belon
2007-11-30 16:28 ` Paul Brook
2007-11-30 17:00   ` Carlo Marcelo Arenas Belon
2007-11-30 17:15     ` Paul Brook
2007-11-30 17:24       ` Blue Swirl
2007-12-01  1:19       ` Paul Mundt [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=20071201011906.GB15027@linux-sh.org \
    --to=lethal@linux-sh.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 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.