qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] sh4: define explicitly that the target CPU is 32 bit
Date: Fri, 30 Nov 2007 19:24:21 +0200	[thread overview]
Message-ID: <f43fc5580711300924k3f568b58ld3b49044bcdb8144@mail.gmail.com> (raw)
In-Reply-To: <200711301715.21956.paul@codesourcery.com>

On 11/30/07, Paul Brook <paul@codesourcery.com> wrote:
> On Friday 30 November 2007, Carlo Marcelo Arenas Belon wrote:
> > On Fri, Nov 30, 2007 at 04:28:09PM +0000, Paul Brook wrote:
> > > On Friday 30 November 2007, Carlo Marcelo Arenas Belon wrote:
> > > > The following patch enforces that the sh4 target is 32 bit to prevent
> > > > qemu to expand incorrectly to a 64 bit wide cpu if compiled in a 64 bit
> > > > host.
> > >
> > > This is wrong. As the comment in cpu-defs.h says, target_phys_addr_t may
> > > need to be bigger than the actual target address space.
> > >
> > > What exactly are you trying to fix?
> >
> > in a generic way, that the CPU width of the host (as defined by the size of
> > the type that is used to store a target_phys_addr_t) that is used to build
> > the emulator affects in any way the size of the emulated target physical
> > address size or its representation.
> >
> > 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.

36 bits. ASI bits could be included to address bits in order to
simplify the ASI handling, then the sum would be 43 or 44.

  reply	other threads:[~2007-11-30 17:34 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 [this message]
2007-12-01  1:19       ` Paul Mundt

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