From: "Kevin D. Kissell" <kevink@mips.com>
To: "Ralf Baechle" <ralf@oss.sgi.com>
Cc: "Harald Koerfgen" <Harald.Koerfgen@home.ivm.de>,
<linux-mips@oss.sgi.com>
Subject: Re: MIPS32 patches breaking DecStation
Date: Tue, 9 Jan 2001 21:33:12 +0100 [thread overview]
Message-ID: <01c201c07a7b$696b9c40$0deca8c0@Ulysses> (raw)
In-Reply-To: 20010109175416.A5383@bacchus.dhis.org
> > Yes, it's cute, but it relies on accidents of implementation to work,
> > and could easily fail on other CPUs otherwise compatible with
> > the R4000. In principle, such a branch might incur no delay at
> > all on an advanced 64-bit processor. By all means, use it for
> > the specific cases of the CPUs on which it is known to work,
> > but it should not be used in "default" MIPS CP0 handlers.
>
> This behaviour of the R4000 branch is documented in the R4000 manual's
> description of the pipeline.
Yes, yes, like I said, use it whenever you see an R4000 PrID
if you like. Just don't use it as the handler installed for a PrID
not otherwise known to the kernel.
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Harald Koerfgen <Harald.Koerfgen@home.ivm.de>, linux-mips@oss.sgi.com
Subject: Re: MIPS32 patches breaking DecStation
Date: Tue, 9 Jan 2001 21:33:12 +0100 [thread overview]
Message-ID: <01c201c07a7b$696b9c40$0deca8c0@Ulysses> (raw)
Message-ID: <20010109203312.26za5K1dmk2x4vPG72SygEyJfxLWswiF9_tK423HqSg@z> (raw)
In-Reply-To: 20010109175416.A5383@bacchus.dhis.org
> > Yes, it's cute, but it relies on accidents of implementation to work,
> > and could easily fail on other CPUs otherwise compatible with
> > the R4000. In principle, such a branch might incur no delay at
> > all on an advanced 64-bit processor. By all means, use it for
> > the specific cases of the CPUs on which it is known to work,
> > but it should not be used in "default" MIPS CP0 handlers.
>
> This behaviour of the R4000 branch is documented in the R4000 manual's
> description of the pipeline.
Yes, yes, like I said, use it whenever you see an R4000 PrID
if you like. Just don't use it as the handler installed for a PrID
not otherwise known to the kernel.
Kevin K.
next prev parent reply other threads:[~2001-01-09 20:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 23:41 MIPS32 patches breaking DecStation Florian Lohoff
2001-01-08 23:41 ` Florian Lohoff
2001-01-09 0:34 ` Kevin D. Kissell
2001-01-09 0:34 ` Kevin D. Kissell
2001-01-09 8:54 ` Florian Lohoff
2001-01-09 17:11 ` Harald Koerfgen
2001-01-09 18:28 ` Ralf Baechle
2001-01-09 19:30 ` Kevin D. Kissell
2001-01-09 19:30 ` Kevin D. Kissell
2001-01-09 19:54 ` Ralf Baechle
2001-01-09 19:54 ` Ralf Baechle
2001-01-09 20:33 ` Kevin D. Kissell [this message]
2001-01-09 20:33 ` Kevin D. Kissell
2001-01-09 15:09 ` Ralf Baechle
2001-01-09 15:09 ` Ralf Baechle
2001-01-09 15:50 ` Kevin D. Kissell
2001-01-09 15:50 ` Kevin D. Kissell
2001-01-09 16:43 ` Harald Koerfgen
2001-01-09 17:01 ` 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='01c201c07a7b$696b9c40$0deca8c0@Ulysses' \
--to=kevink@mips.com \
--cc=Harald.Koerfgen@home.ivm.de \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@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