From: Ralf Baechle <ralf@oss.sgi.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Kevin D. Kissell" <kevink@mips.com>, "H. J. Lu" <hjl@lucon.org>,
Jun Sun <jsun@mvista.com>,
Linux/MIPS Development <linux-mips@oss.sgi.com>
Subject: Re: Malta crashes on the latest 2.4 kernel
Date: Thu, 11 Jul 2002 13:45:49 +0200 [thread overview]
Message-ID: <20020711134549.B11700@dea.linux-mips.net> (raw)
In-Reply-To: <Pine.GSO.4.21.0207110854250.8371-100000@vervain.sonytel.be>; from geert@linux-m68k.org on Thu, Jul 11, 2002 at 08:56:17AM +0200
On Thu, Jul 11, 2002 at 08:56:17AM +0200, Geert Uytterhoeven wrote:
> On Thu, 11 Jul 2002, Kevin D. Kissell wrote:
> > I note that Ralf has, in fact, applied the fix to the
> > OSS CVS repository. I also note that "BARRIER"
> > is still defined to be a string of 6 nops. I would argue
> > (again) that those really, really ought to be ssnops,
> > and that if they *were* ssnops, one could probably
> > have fewer of them.
>
> Sorry for being ignorant, but what's the difference between nop and ssnop?
>
> I see that SSNOP is defined to be `sll zero,zero,1' in <asm/asm.h>, but that
> doesn't give me any clue.
Ssnop is a superscalar nop. It's instruction encoding is the same as of
sll, zero, zero, 1. Unlike a normal nop a ssnop is guaranteed to single
issue even on superscalar implementations.
Ralf
next prev parent reply other threads:[~2002-07-11 15:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 23:12 Malta crashes on the latest 2.4 kernel Jun Sun
2002-07-10 23:49 ` H. J. Lu
2002-07-11 1:18 ` Jun Sun
2002-07-11 2:36 ` Ralf Baechle
2002-07-11 6:19 ` Kevin D. Kissell
2002-07-11 6:19 ` Kevin D. Kissell
2002-07-11 6:56 ` Geert Uytterhoeven
2002-07-11 8:35 ` Kevin D. Kissell
2002-07-11 11:45 ` Ralf Baechle [this message]
2002-07-11 11:59 ` Ralf Baechle
2002-07-11 7:50 ` Carsten Langgaard
2002-07-11 7:44 ` Carsten Langgaard
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=20020711134549.B11700@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=geert@linux-m68k.org \
--cc=hjl@lucon.org \
--cc=jsun@mvista.com \
--cc=kevink@mips.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.