From: Dave Jones <davej@suse.de>
To: Jean-Marc Saffroy <saffroy@ri.silicomp.fr>
Cc: <linux-kernel@vger.kernel.org>, <linux-smp@vger.kernel.org>
Subject: Re: [Q] Implementation of spin_lock on i386: why "rep;nop" ?
Date: Mon, 17 Sep 2001 18:22:33 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.30.0109171821340.27689-100000@Appserv.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.31.0109171725140.26090-100000@sisley.ri.silicomp.fr>
On Mon, 17 Sep 2001, Jean-Marc Saffroy wrote:
> What is the intent behind this "rep;nop" ? Does it really rely on an
> undocumented behaviour ?
Its used to stop Pentium 4's from cooking themselves.
See the P4 manuals for more info.
regards,
Dave.
--
| Dave Jones. http://www.suse.de/~davej
| SuSE Labs
next prev parent reply other threads:[~2001-09-17 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 16:16 [Q] Implementation of spin_lock on i386: why "rep;nop" ? Jean-Marc Saffroy
2001-09-17 16:22 ` Dave Jones [this message]
2001-09-17 17:19 ` Jean-Marc Saffroy
2001-09-17 16:42 ` Richard B. Johnson
2001-09-17 17:06 ` Jonathan Lundell
2001-09-17 17:27 ` Alan Cox
2001-09-17 19:47 ` H. Peter Anvin
2001-09-19 3:42 ` Jamie Lokier
2001-09-19 4:06 ` Brian Gerst
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=Pine.LNX.4.30.0109171821340.27689-100000@Appserv.suse.de \
--to=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-smp@vger.kernel.org \
--cc=saffroy@ri.silicomp.fr \
/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).