mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: davej@suse.de, johnstul@us.ibm.com
Cc: Martin.Bligh@us.ibm.com, linux-kernel@vger.kernel.org,
	marcelo@conectiva.com.br
Subject: Re: [Patch] tsc-disable_A5
Date: Fri, 14 Jun 2002 23:53:09 +0200 (MET DST)	[thread overview]
Message-ID: <200206142153.XAA03026@harpo.it.uu.se> (raw)

On Fri, 14 Jun 2002 21:56:54 +0200, Dave Jones wrote:
>On Fri, Jun 14, 2002 at 12:04:18PM -0700, john stultz wrote:
>
> > .config that looked like:
> > 
> > CONFIG_X86_TSC=y
> > ...
> > # CONFIG_X86_TSC is not set
> > So I assumed CONFIG_X86_TSC would still hold. Am I wrong, or is there
> > another way to do this?
>
>Ugh, I hadn't realised the .config generation was so primitive.
>That's quite unfortunate. That needs fixing at some point.

Unless my memory is failing me, I believe the simplest approach
is to (1) don't set CONFIG_X86_TSC, and (2) pass "notsc" as a
kernel boot parameter.

CONFIG_X86_TSC means "the machine has working TSC, period".
That's an intensional optimisation.

Without CONFIG_X86_TSC, Linux manages without TSC, but will
detect and use it if it's there.

Finally, the "notsc" kernel parameter is for obscure cases
where the TSC is present, but should not be used for whatever
reason. I guess the present issue qualifies...

/Mikael

             reply	other threads:[~2002-06-14 21:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-14 21:53 Mikael Pettersson [this message]
2002-06-14 22:11 ` john stultz
  -- strict thread matches above, loose matches on Subject: below --
2002-06-15 14:13 Mikael Pettersson
2002-06-19 13:58 ` Maciej W. Rozycki
2002-06-14 18:35 john stultz
2002-06-14 18:53 ` Benjamin LaHaise
2002-06-18  0:48   ` Kurt Garloff
2002-06-18  1:31     ` john stultz
2002-06-14 18:57 ` Dave Jones
2002-06-14 19:04   ` john stultz
2002-06-14 19:56     ` Dave Jones
2002-06-14 23:29       ` Kai Germaschewski
2002-06-14 23:44         ` john stultz
2002-06-24  2:09 ` Pavel Machek

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=200206142153.XAA03026@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=davej@suse.de \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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®