From: "Kevin D. Kissell" <kevink@mips.com>
To: <linux-mips@oss.sgi.com>,
"Thiemo Seufer" <ica2_ts@csv.ica.uni-stuttgart.de>
Subject: Re: mips64 linker bug?
Date: Sun, 22 Jul 2001 13:44:37 +0200 [thread overview]
Message-ID: <007d01c112a3$b10134a0$0deca8c0@Ulysses> (raw)
In-Reply-To: 20010722131525.L16278@rembrandt.csv.ica.uni-stuttgart.de
> Kevin D. Kissell wrote:
> [snip]
> > > An Kernel with 64bit addresses is less compact and likely to run
slower.
> > > OTOH, a 64bit Kernel has certainly some hack value. :-)
> >
> > Note that the 5Kc is one of the new generation of MIPS64 parts
> > that can enable 64-bit integer and floating point instructions without
> > requiring that 64-bit addressing also be enabled in the kernel.
>
> Sorry, but I can't see what's new here. AFAICS this possibility existed
> already in MIPS III.
Sorry if I wasn't clear. It is only the newer parts that can enable the
use of the 64-bit instructions *in user mode* without also enabling
64-bit addressng. It's true that MIPS III/IV parts provide access to
those instructions in kernel regardless of the state of the Status.KX
bit, but in user mode they are only available if the Status.UX bit is set,
enabling 64-bit addressing. MIPS64 CPU's have an additional
bit in the Status register (Bit 23, "PX") to enable 64-bit instructions
without enabling 64-bit addressing.
Regards,
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: linux-mips@oss.sgi.com, Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Subject: Re: mips64 linker bug?
Date: Sun, 22 Jul 2001 13:44:37 +0200 [thread overview]
Message-ID: <007d01c112a3$b10134a0$0deca8c0@Ulysses> (raw)
Message-ID: <20010722114437.nSRw1FFW-JcgqkqVx0VKzQ1Goftkxxd8SPEAY_snktg@z> (raw)
In-Reply-To: 20010722131525.L16278@rembrandt.csv.ica.uni-stuttgart.de
> Kevin D. Kissell wrote:
> [snip]
> > > An Kernel with 64bit addresses is less compact and likely to run
slower.
> > > OTOH, a 64bit Kernel has certainly some hack value. :-)
> >
> > Note that the 5Kc is one of the new generation of MIPS64 parts
> > that can enable 64-bit integer and floating point instructions without
> > requiring that 64-bit addressing also be enabled in the kernel.
>
> Sorry, but I can't see what's new here. AFAICS this possibility existed
> already in MIPS III.
Sorry if I wasn't clear. It is only the newer parts that can enable the
use of the 64-bit instructions *in user mode* without also enabling
64-bit addressng. It's true that MIPS III/IV parts provide access to
those instructions in kernel regardless of the state of the Status.KX
bit, but in user mode they are only available if the Status.UX bit is set,
enabling 64-bit addressing. MIPS64 CPU's have an additional
bit in the Status register (Bit 23, "PX") to enable 64-bit instructions
without enabling 64-bit addressing.
Regards,
Kevin K.
next prev parent reply other threads:[~2001-07-22 11:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-21 9:27 mips64 linker bug? Lars Munch Christensen
2001-07-21 15:23 ` Ralf Baechle
2001-07-21 16:17 ` Lars Munch Christensen
2001-07-21 19:07 ` Ralf Baechle
2001-07-22 9:39 ` Lars Munch Christensen
2001-07-22 10:35 ` Thiemo Seufer
2001-07-22 11:02 ` Kevin D. Kissell
2001-07-22 11:02 ` Kevin D. Kissell
2001-07-22 11:15 ` Thiemo Seufer
2001-07-22 11:44 ` Kevin D. Kissell [this message]
2001-07-22 11:44 ` Kevin D. Kissell
2001-07-22 21:23 ` Ralf Baechle
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='007d01c112a3$b10134a0$0deca8c0@Ulysses' \
--to=kevink@mips.com \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=linux-mips@oss.sgi.com \
/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