qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH, MIPS64] Implement per CPU SEGBITS value
Date: Sat, 23 Jun 2007 09:41:11 +0100	[thread overview]
Message-ID: <20070623084110.GA9170@networkno.de> (raw)
In-Reply-To: <20070613183940.GC25272@amd64.aurel32.net>

Aurelien Jarno wrote:
> Hi!
> 
> The current MIPS64 implementation assumes SEGBITS = 40 for all CPU. This
> is correct for most CPU, but wrong for example for the 5K one, which has
> SEGBITS = 42.
> 
> This patch modifies the current code to use SEGBITS instead of an 
> hardcoded value. Instead of recomputing the corresponding mask each time
> the value is computed in translate_init and stored in env.

Looks good, except that it breaks for me mips64el-softmmu...
It hangs at the startup of userland.


Thiemo

  reply	other threads:[~2007-06-23  8:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-13 18:39 [Qemu-devel] [PATCH, MIPS64] Implement per CPU SEGBITS value Aurelien Jarno
2007-06-23  8:41 ` Thiemo Seufer [this message]
2007-06-23 13:23   ` Aurelien Jarno

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=20070623084110.GA9170@networkno.de \
    --to=ths@networkno.de \
    --cc=aurelien@aurel32.net \
    --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).