public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Raffaele Sandrini <rasa@gmx.ch>
To: linux-kernel@vger.kernel.org
Subject: Re: System clock and speedstepping
Date: Tue, 2 Dec 2003 23:16:21 +0100	[thread overview]
Message-ID: <200312022316.21477.rasa@gmx.ch> (raw)
In-Reply-To: <1070318452.23568.577.camel@cog.beaverton.ibm.com>

On Monday 01 December 2003 23:40, john stultz wrote:
>
> The "sane timesource" is the PIT (programmable interval timer). The TSC
> is the Time-Stamp-Counter which is basically a cycle counter on the cpu.
> If you want to boot using the PIT instead of the TSC, you can override
> the default time source by using  "clock=pit" as a boot option. However
> hopefully the problem can be fixed by adjusting the cpufreq code. As I
> don't have any such hardware, would you be interested in testing
> possible patches?
>
> thanks
> -john
>

Im willing to solve it another way: There is a patch around (included in the 
mm paches) for the kernel wich introduces a ACPI timer (timesource). As im 
successfully using ACPI here ill switch over to it. A collegue of mine (who 
had equal problems) reportet that this driver solves the problem completly.

About your patches: I would surely test your patches... i think its necessray 
to have a good bug less standard implementation  of the timesource.

BTW: The time screw was huge. Especially if i ran programms wich needed all 
the recources avalible (while(1){}).

cheers,
Raffaele
-- 
Raffaele Sandrini <rasa@gmx.ch>


  reply	other threads:[~2003-12-02 22:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-28 16:09 System clock and speedstepping Raffaele Sandrini
2003-12-01 22:40 ` john stultz
2003-12-02 22:16   ` Raffaele Sandrini [this message]
2003-12-03  0:56     ` john stultz

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=200312022316.21477.rasa@gmx.ch \
    --to=rasa@gmx.ch \
    --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