public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Zwane Mwaikambo <zwane@holomorphy.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Mikael Pettersson <mikpe@csd.uu.se>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][2.5] notsc option needs some attention/TLC
Date: Mon, 11 Nov 2002 00:15:50 -0800	[thread overview]
Message-ID: <20021111081550.GN23425@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0211101747420.12703-100000@home.transmeta.com>

On Sun, Nov 10, 2002 at 05:51:37PM -0800, Linus Torvalds wrote:
> But that's the point. If you specify that you have a CPU > 586, then you 
> specify at compile-time that you have TSC.
> If your TSC is broken, then you shouldn't do that. You should compile for 
> "generic x86" (386), and then say "notsc".
> (Yeah, it should work for i486 too, but in general it's the "generic 386"  
> that should work on all machines because it doesn't assume anything about
> the capabilities of the machine).
> But considering that we don't use the static TSC knowledge very much any
> more, you might want to remove CONFIG_X86_TSC altogether, though, and
> replace its uses with run-time checks. We've done that with a lot of the
> other config stuff earlier (SSE/XMM) because the static compiled options
> are just too inconvenient and not worth the maintenance hassles..

Performance considerations make compiling for 386 a relatively poor
solution. I'm very much in favor of the runtime checks and will
intensively investigate that method of dealing with the situation, and
with any luck follow up soon with a solution acceptable to both you and
others for this dynamic TSC usage issue.


Thanks,
Bill

  reply	other threads:[~2002-11-11  8:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-09 12:00 [PATCH][2.5] notsc option needs some attention/TLC Mikael Pettersson
2002-11-09 13:05 ` Alan Cox
2002-11-09 16:34   ` Martin J. Bligh
2002-11-09 18:09   ` Zwane Mwaikambo
2002-11-09 18:51     ` Linus Torvalds
2002-11-10 19:03       ` Henning P. Schmiedehausen
2002-11-12 11:29         ` Maciej W. Rozycki
2002-11-11  1:21       ` William Lee Irwin III
2002-11-11  1:51         ` Linus Torvalds
2002-11-11  8:15           ` William Lee Irwin III [this message]
2002-11-11 13:24           ` Alan Cox
2002-11-09 19:10     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-11-09 17:52 J.E.J. Bottomley
2002-11-10  5:32 ` Zwane Mwaikambo
2002-11-10 14:25   ` J.E.J. Bottomley
2002-11-09  4:52 Zwane Mwaikambo

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=20021111081550.GN23425@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=torvalds@transmeta.com \
    --cc=zwane@holomorphy.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