From: Andrew Morton <akpm@digeo.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: torvalds@transmeta.com, johnstul@us.ibm.com,
linux-kernel@vger.kernel.org, coop@axian.com
Subject: Re: [PATCH] boot time parameter to turn of TSC usage
Date: Tue, 18 Mar 2003 16:39:02 -0800 [thread overview]
Message-ID: <20030318163902.2572ab6f.akpm@digeo.com> (raw)
In-Reply-To: <1048034299.6296.85.camel@dell_ss3.pdx.osdl.net>
Stephen Hemminger <shemminger@osdl.org> wrote:
>
> For machines that don't want to cooperate and have bad TSC counter and/or
> change CPU frequency without change support.
>
> This fixes the problem on Jerry Cooperstein's PIII laptop.
> Could be useful for other people and tech support situations.
Is there no way in which this can be auto-detected?
> +__setup("notsclock", tsc_noclock_setup);
People have recently worked to make Documentation/kernel-parameters.txt
relatively up-to-date. Please try to remember to keep it in sync...
next prev parent reply other threads:[~2003-03-19 0:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 19:05 seqlock/unlock(&xtime_lock) problems cause keyboard, time skew problems Jerry Cooperstein
2003-03-18 20:32 ` Stephen Hemminger
2003-03-18 20:59 ` Jerry Cooperstein
2003-03-18 23:34 ` john stultz
2003-03-19 0:21 ` Jerry Cooperstein
2003-03-19 0:38 ` [PATCH] boot time parameter to turn of TSC usage Stephen Hemminger
2003-03-19 0:39 ` Andrew Morton [this message]
2003-03-19 1:03 ` Stephen Hemminger
2003-03-18 23:57 ` seqlock/unlock(&xtime_lock) problems cause keyboard, time skew problems Stephen Hemminger
[not found] ` <1048022686.6291.6.camel@dell_ss3.pdx.osdl.net>
[not found] ` <20030318214101.GA4527@p3.attbi.com>
[not found] ` <1048025052.6294.16.camel@dell_ss3.pdx.osdl.net>
[not found] ` <20030318222313.GA4831@p3.attbi.com>
[not found] ` <1048027027.6297.33.camel@dell_ss3.pdx.osdl.net>
[not found] ` <20030318225801.GC4831@p3.attbi.com>
[not found] ` <1048030151.6297.71.camel@dell_ss3.pdx.osdl.net>
2003-03-19 0:27 ` Jerry Cooperstein
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=20030318163902.2572ab6f.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=coop@axian.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.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
all inboxes | Powered by JetHome®