From: Ingo Molnar <mingo@elte.hu>
To: Ben Greear <greearb@candelatech.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Yinghai Lu <yinghai@kernel.org>,
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: Thu, 5 Feb 2009 22:02:39 +0100 [thread overview]
Message-ID: <20090205210239.GD21500@elte.hu> (raw)
In-Reply-To: <498B4E44.9080607@candelatech.com>
* Ben Greear <greearb@candelatech.com> wrote:
> Ingo Molnar wrote:
>> * Ben Greear <greearb@candelatech.com> 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.
>>>
>>> This is against 2.6.29-rc3.
>>
>> What 'issues' does that work around, exactly?
>
> Without this, my system comes up with no stable high-res
> clock, and the getnstimeofday seems to return something
> with around 1ms granularity. I have HZ set to 1000, so
> its probably just using the 'jiffy' clocksource.
> This in turn screws up my patched version of pktgen and
> likely is sub-optimal for other things as well.
>
> It seems the TSC on this system is stable, but I got lost
> trying to understand the watchdog testing code, so I'm
> not certain if it is wrong or not. With this force in
> place, the system seems stable and ran overnight under
> network load fine.
What does this tool output:
http://people.redhat.com/mingo/time-warp-test/time-warp-test.c
? (you can run it both the patched or on the unpatched system)
Ingo
next prev parent reply other threads:[~2009-02-05 21:02 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 [this message]
2009-02-05 21:18 ` Frans Pop
2009-02-06 14:36 ` Jiri Kosina
2009-02-06 17:52 ` Ben Greear
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=20090205210239.GD21500@elte.hu \
--to=mingo@elte.hu \
--cc=greearb@candelatech.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=yinghai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.