public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, rusty@rustcorp.com.au
Subject: Re: PATCH:  Allow user to force 'tsc' to be treated as stable.
Date: Fri, 06 Feb 2009 09:52:09 -0800	[thread overview]
Message-ID: <498C78C9.5090405@candelatech.com> (raw)
In-Reply-To: <alpine.LRH.1.10.0902061531560.22097@twin.jikos.cz>

Jiri Kosina wrote:
> On Thu, 5 Feb 2009, Ben Greear wrote:
> 
>> Allow user to force TSC as stable clock-source. Works around BIOS issues 
>> in the FWA-7304 (Via CN700 chipset) system, and possibly others.
> 
> How do you know that the TSC is stable on such system? What was the reason 
> for kernel marking it unstable?

I've used it for a timing source in my own modules and it has
worked well.  It could still be broken in some way, but if so,
I'm not sure how to detect it.  Ingo sent me a program to test
the tsc, and at least for short runs, it showed no problem.

Another person suggested the system might think it is unstable
because I have ACPI disabled in my BIOS and that might cause
the kernel not to have a 'PM timer' that it uses to check the
tsc?

Other than that, I have no idea why the kernel thinks the tsc
is unstable.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2009-02-06 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05 19:49 PATCH: Allow user to force 'tsc' to be treated as stable Ben Greear
2009-02-05 19:59 ` Ingo Molnar
2009-02-05 20:38   ` Ben Greear
2009-02-05 21:02     ` Ingo Molnar
2009-02-05 21:18 ` Frans Pop
2009-02-06 14:36 ` Jiri Kosina
2009-02-06 17:52   ` Ben Greear [this message]
2009-02-06 19:40     ` Thomas Gleixner
2009-02-06 23:24     ` Jiri Kosina

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=498C78C9.5090405@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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