mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Lyle Coder" <x_coder@hotmail.com>
To: "Andre Hedrick" <andre@linux-ide.org>,
	"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Frank Davis" <fdavis112@juno.com>, <linux-kernel@vger.kernel.org>
Subject: Re: Pentium 4 and 2.4/2.5
Date: Tue, 7 Nov 2000 13:06:11 -0800	[thread overview]
Message-ID: <OE59dY2pjID9Lv40q2H00001e2c@hotmail.com> (raw)
In-Reply-To: <E13t7dG-0007KT-00@the-village.bc.nu>

Alan,
are you saying that rep;nop is not needed in the spinlocks? (because they
are for P4)

Thanks
Lyle
----- Original Message -----
From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
To: "Andre Hedrick" <andre@linux-ide.org>
Cc: "Frank Davis" <fdavis112@juno.com>; <linux-kernel@vger.kernel.org>
Sent: Tuesday, November 07, 2000 4:13 AM
Subject: Re: Pentium 4 and 2.4/2.5


> > Not to worry, some of us are working with the 'I' guys to do proper P4
> > detection.
>
> Be careful with the intel patches. The ones I've seen so far tried to call
the
> cpu 'if86' breaking several tools that do cpu model checking off uname.
They
> didnt fix the 2GHz CPU limit, they use 'rep nop' in the locks which is
> explicitly 'undefined behaviour' for non intel processors and they use the
> TSC without checking it had one.
>
> Hopefully they have improved since
>
> Alan
>
> -
> 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/
>
-
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/

  reply	other threads:[~2000-11-07 21:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2000-11-05  0:04 Frank Davis
2000-11-08  0:43 ` 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=OE59dY2pjID9Lv40q2H00001e2c@hotmail.com \
    --to=x_coder@hotmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andre@linux-ide.org \
    --cc=fdavis112@juno.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®