[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51D61FF2.8050302@intel.com>
Date: Fri, 05 Jul 2013 09:22:58 +0800
From: Alex Shi <alex.shi@...el.com>
To: Thomas Gleixner <tglx@...utronix.de>
CC: hpa@...ux.intel.com, tim.c.chen@...ux.intel.com,
linux-kernel@...r.kernel.org, andi.kleen@...el.com,
a.p.zijlstra@...llo.nl, mingo@...e.hu
Subject: Re: [PATCH 1/3] clocksource: clean up clocksource_select
On 07/04/2013 06:27 PM, Thomas Gleixner wrote:
>> > BTW, why we allow user override a second best clocksource? I mean user
>> > can override the tsc with hpet. because undetected unstable tsc?
> The user can decide to override with clocksource=jiffies if he wants
> for testing purposes. That wont switch into highres ever if done from
> the kernel command line. Now we have a sysfs interface, so we need to
> sanity check the user override against highres.
>
> The override is quite useful to test hpet, pmtimer on a machine which
> would always select TSC.
Got it. thanks a lot for friendly explanation!
--
Thanks
Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists