mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Valdis.Kletnieks@vt.edu
Cc: Rob Love <rml@ximian.com>, linux-kernel@vger.kernel.org
Subject: Re: Pentium M config option for 2.6
Date: Sun, 4 Jan 2004 22:55:41 +0100	[thread overview]
Message-ID: <20040104215541.GB14982@ucw.cz> (raw)
In-Reply-To: <200401042034.i04KYm1P024587@turing-police.cc.vt.edu>

On Sun, Jan 04, 2004 at 03:34:47PM -0500, Valdis.Kletnieks@vt.edu wrote:
> On Sun, 04 Jan 2004 11:33:08 EST, Rob Love said:
> 
> > I actually like this patch (perhaps since I have a P-M :) and think it
> > ought to go in, although I agree with others that the P-M is more of a
> > super-P3 than a scaled down P4.
> 
> Same here - /proc/cpuinfo says:
> 
> vendor_id       : GenuineIntel
> cpu family      : 15
> model           : 2
> model name      : Intel(R) Pentium(R) 4 Mobile CPU 1.60GHz
> 
> Question for those more knowledgeable: Are there any known Pentium4 features
> enabled in the kernel with the PENTIUM4 options that simply Will Not Work on a
> 4M chipset (similar to a kernel built for a 586 not working on a 486), or are
> the differences limited to "sub-optimal performance" (for example, compiling
> with -mpentium4 results in code that runs but schedules less optimally)?  If
> there are, they must be fairly obscure corner cases, since I haven't knowingly
> hit one in several months.. :)
> 
> 2.7 timeframe - are there any added features of a P4 core we would *like*
> to exploit that aren't on a P4M?

Pentium 4M is a real Pentium 4 core, but with mobile features.

Pentium M is a beefed up Pentium III core, with mobile features and all
		Pentium 4 extra features (instructions, etc).

I think that answers your question.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2004-01-04 21:55 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-04 12:27 Mikael Pettersson
2004-01-04 12:33 ` Tomas Szepe
2004-01-06  6:07   ` Jakob Oestergaard
2004-03-29 15:46   ` Jakob Oestergaard
2004-01-04 15:03 ` Rob Love
2004-01-04 16:25   ` Dave Jones
2004-01-04 16:33     ` Rob Love
2004-01-04 16:50       ` Dave Jones
2004-01-04 17:01         ` Rob Love
2004-01-04 17:14           ` Tomas Szepe
2004-03-29 15:42           ` Tomas Szepe
2004-01-04 17:03         ` Troels Walsted Hansen
2004-01-04 17:35           ` Dave Jones
2004-01-04 21:51         ` Vojtech Pavlik
2004-03-29 15:42         ` Rob Love
2004-01-04 20:34       ` Valdis.Kletnieks
2004-01-04 21:55         ` Vojtech Pavlik [this message]
2004-01-04 23:37           ` Valdis.Kletnieks
2004-03-29 15:42       ` Dave Jones
2004-03-29 15:42     ` Rob Love
2004-03-29 15:42   ` Dave Jones
2004-03-29 15:42 ` Tomas Szepe
2004-03-29 15:42 ` Rob Love
  -- strict thread matches above, loose matches on Subject: below --
2004-03-29 15:42 Mikael Pettersson
2004-03-29 15:42 Mikael Pettersson
2004-01-05 15:09 Amit Gurdasani
2004-01-05 15:22 ` Tim Schmielau
2004-01-04 14:10 Mikael Pettersson
2004-01-04 14:43 ` Tomas Szepe
2004-01-04 15:59   ` Ciaran McCreesh
2004-03-29 15:42   ` Ciaran McCreesh
2004-03-29 15:42 ` Tomas Szepe
2004-01-04  2:28 Tomas Szepe

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=20040104215541.GB14982@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@ximian.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

all inboxes | Powered by JetHome®