From: Dave Jones <davej@suse.de>
To: Greg KH <greg@kroah.com>
Cc: Gordon J Lee <gordonl@world.std.com>, linux-kernel@vger.kernel.org
Subject: Re: IBM x360 2.2.x boot failure, 2.4.9 works fine
Date: Sat, 16 Mar 2002 20:54:40 +0100 [thread overview]
Message-ID: <20020316205440.C15296@suse.de> (raw)
In-Reply-To: <3C927F3E.7C7FB075@world.std.com> <20020315234333.GH5563@kroah.com> <3C92B1EA.F40BDBD5@world.std.com> <20020316055542.GA8125@kroah.com> <3C938093.D1640CB6@world.std.com> <20020316173434.GB10003@kroah.com> <3C938693.6D29979C@world.std.com> <20020316194025.GA10571@kroah.com>
In-Reply-To: <20020316194025.GA10571@kroah.com>
On Sat, Mar 16, 2002 at 11:40:25AM -0800, Greg KH wrote:
> > If so, at which 2.4.x kernel did support for hyperthreading show up?
> In one of the 2.4.19-ac kernels from what I remember, sorry I don't know
> the exact version.
Interesting changelog entries..
2.4.14: hyperthreaded P4's
2.4.17:- Pentium IV Hyperthreading support (Alan Cox)
2.4.18ac:o Hyperthreading awareness for MTRR driver
Shame that .14 and .17 aren't more descriptive. I'm guessing
that they provided different bits. Not sure from memory what order
things happened though.
Maybe .14 was "Boot, and don't do anything silly" patches, whilst
.17 was the actual "take advantage of this feature" patch.
*shrug*
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-03-16 19:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 23:09 IBM x360 2.2.x boot failure, 2.4.9 works fine Gordon J Lee
2002-03-15 23:34 ` Greg KH
2002-03-16 0:06 ` James Cleverdon
2002-03-16 1:50 ` Gordon J Lee
2002-03-16 5:58 ` Greg KH
2002-03-17 19:43 ` Jack F. Vogel
2002-03-15 23:43 ` Greg KH
2002-03-16 2:46 ` Gordon J Lee
2002-03-16 5:55 ` Greg KH
2002-03-16 17:27 ` Gordon J Lee
2002-03-16 17:34 ` Greg KH
2002-03-16 17:53 ` Gordon J Lee
2002-03-16 19:40 ` Greg KH
2002-03-16 19:54 ` Dave Jones [this message]
2002-03-16 20:51 ` 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=20020316205440.C15296@suse.de \
--to=davej@suse.de \
--cc=gordonl@world.std.com \
--cc=greg@kroah.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