public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Davis <fdavis112@juno.com>
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com, alan@orguk.ukuu.org.uk, fdavis112@juno.com
Subject: Pentium IV-summary
Date: Wed, 8 Nov 2000 15:14:22 -0500 (EST)	[thread overview]
Message-ID: <379322493.973714466779.JavaMail.root@web346-wra.mail.com> (raw)

Hello,

I think I have summarized the discussion for clarity: 

1. rep nop can used with all x86 boxes, unless a valid example can be found where it doesn't work. Athlon works with the rep nop. 

2. There's a bug in get_model_name(),
   cpuid(0x80000001, &dummy, &dummy, &dummy, &(c->x86_capability));

that overwrites the capability state. It will be fixed in 2.2.18  by Dave Jones. Should we also look at Peter Anvin's fix for the problem that Linus mentioned? What are the other features of the Pentium IV should be included in the kernel pending the capability state fix?

3. 2.4.x may support processor speeds up to 100GHz, as well as Pentium IV. Linus will have a Pentium IV available soon, but can someone test the kernel with a Pentium IV sooner?

Regards,
Frank


-
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-08 20:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-08 20:14 Frank Davis [this message]
2000-11-08 20:36 ` Pentium IV-summary H. Peter Anvin
2000-11-08 20:47   ` David Weinehall
2000-11-08 22:45     ` Alan Cox
2000-11-09  0:16       ` H. Peter Anvin
2000-11-09  0:46 ` Prasanna P Subash
  -- strict thread matches above, loose matches on Subject: below --
2000-11-08 20:14 Frank Davis

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=379322493.973714466779.JavaMail.root@web346-wra.mail.com \
    --to=fdavis112@juno.com \
    --cc=alan@orguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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