[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131007155937.GT26785@twins.programming.kicks-ass.net>
Date: Mon, 7 Oct 2013 17:59:37 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Adrian Hunter <adrian.hunter@...el.com>, hpa@...or.com,
linux-kernel@...r.kernel.org, tglx@...utronix.de,
linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] perf/x86: Clean up cap_user_time* setting
On Mon, Oct 07, 2013 at 11:33:22AM +0200, Peter Zijlstra wrote:
> On Sun, Oct 06, 2013 at 11:10:54AM +0200, Ingo Molnar wrote:
> > I'm fully with you, please zap the 'notsc' boot option - it's an ancient
> > relic, if any box is still broken with the TSC on we want to hear about it
> > and fix it!
>
> something like so?
>
> ---
> Subject: x86: Remove 'notsc' option for X86_TSC=y kernels
>
> The 'notsc' thing is an ancient relic, if there's still any hardware
> that needs this we need to hear about it.
>
> This only removes the option for X86_TSC=y kernels; X86_TSC=n kernels
> can still use it to force remove the TSC capability flag.
>
> Since this removes the tsc_disabled=1 assignment, also remove all
> tsc_disabled>0 tests as those will never be true.
>
> Suggested-by: Ingo Molnar <mingo@...nel.org>
> Signed-off-by: Peter Zijlstra <peterz@...radead.org>
OK, so I forgot to compile this this morning; but I now found
apicpmtimer somehow calls notsc_setup(). I've no idea why, but can
someone who knows this crap take a look?
--
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