From: Frank Davis <fdavis112@juno.com>
To: alan@lxorguk.ukuu.org.uk
Cc: x_coder@hotmail.com, andre@linux-ide.org, linux-kernel@vger.kernel.org
Subject: Re: Pentium 4 and 2.4/2.5
Date: Sat, 4 Nov 2000 19:04:08 -0500 [thread overview]
Message-ID: <20001104.190410.-351455.2.fdavis112@juno.com> (raw)
Alan,
As for 'rep nop', couldn't we add in the code, as an example:
#ifdef Pentium_4
rep nop
#endif
As for the 2.2.18 patch for correctly determining 2GHz and above, can
it be easily merged into the 2.4.x kernel, and if so, what's the maximum
clock speed that can be detected?
Regards,
-Frank
On Tue, 7 Nov 2000 21:48:40 +0000 (GMT) Alan Cox
<alan@lxorguk.ukuu.org.uk> writes:
> > are you saying that rep;nop is not needed in the spinlocks?
> (because they
> > are for P4)
>
> rep;nop is a magic instruction on the PIV and possibly some PIII
> series CPUs
> [not sure]. As far as I can make out it naps momentarily or until
> bus
> activity thus saving power on spinlocks.
>
> The problem is 'rep nop' is not defined on other cpus so we can only
> really use
> it on the PIII/PIV kernel builds
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-07 23:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-05 0:04 Frank Davis [this message]
2000-11-08 0:43 ` Pentium 4 and 2.4/2.5 Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2000-11-04 23:36 Frank Davis
2000-11-07 3:41 ` Andre Hedrick
2000-11-07 12:13 ` Alan Cox
2000-11-07 21:06 ` Lyle Coder
2000-11-07 21:48 ` Alan Cox
2000-11-08 17:31 ` Linus Torvalds
2000-11-08 17:26 ` Linus Torvalds
2000-11-08 17:50 ` Alan Cox
2000-11-08 18:10 ` Linus Torvalds
2000-11-08 18:12 ` Brian Pomerantz
2000-11-08 18:21 ` Alan Cox
2000-11-08 18:27 ` kernel
2000-11-08 18:47 ` Alan Cox
2000-11-09 20:42 ` Simon Kirby
2000-11-08 18:29 ` Brian Pomerantz
2000-11-08 18:17 ` Alan Cox
2000-11-07 4:01 ` Robert M. Love
2000-11-07 12:04 ` Alan Cox
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=20001104.190410.-351455.2.fdavis112@juno.com \
--to=fdavis112@juno.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x_coder@hotmail.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