From: "M. Warner Losh" <imp@bsdimp.com>
To: arnaud.patard@rtp-net.org
Cc: paul@codesourcery.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fix configure for mips o32
Date: Fri, 05 Jun 2009 01:29:32 -0600 (MDT) [thread overview]
Message-ID: <20090605.012932.-1325212215.imp@bsdimp.com> (raw)
In-Reply-To: <87r5y0tkzg.fsf@lechat.rtp-net.org>
In message: <87r5y0tkzg.fsf@lechat.rtp-net.org>
Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org> writes:
: Paul Brook <paul@codesourcery.com> writes:
:
: Hi,
:
: > On Wednesday 03 June 2009, Arnaud Patard wrote:
: >> Paul Brook <paul@codesourcery.com> writes:
: >> > On Wednesday 03 June 2009, Arnaud Patard wrote:
: >> >> The commit 1ad2134f914dfd4c8f92307c94c9a5a1e28f0059 is defining
: >> >> target_phys_bits and set it to 64 for all mips machines including mipsel
: >> >> machines which are 32 bit. This patch set it to 32.
: >> >
: >> > MIPS32 CPUs have a 36-bit physical address space. That's what the old
: >> > code said anyway.
: >>
: >> Is there more information than that in the old code ? I really thought
: >> mips32 4Kc have 32-bit address paths not 36.
: >
: > I suspect you're confusing physical and virtual addresses.
: >
:
: fwiw, found out where I read that. At
: http://www.mips.com/products/processors/hard-ip-cores/4kc-hard-ip-core/.
None-the-less, mipsel for arc has 36-bit addresses. The patch is bad.
Warner
next prev parent reply other threads:[~2009-06-05 7:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 12:28 [Qemu-devel] [PATCH] fix configure for mips o32 Arnaud Patard
2009-06-03 14:29 ` M. Warner Losh
2009-06-03 15:17 ` Arnaud Patard
2009-06-03 14:46 ` Paul Brook
2009-06-03 15:20 ` Arnaud Patard
2009-06-03 15:22 ` Paul Brook
2009-06-04 9:18 ` Arnaud Patard
2009-06-05 7:29 ` M. Warner Losh [this message]
2009-06-03 15:34 ` M. Warner Losh
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=20090605.012932.-1325212215.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=arnaud.patard@rtp-net.org \
--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).