[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <878shmuu2k.fsf@nanos.tec.linutronix.de>
Date: Thu, 21 May 2020 00:20:51 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Peter Zijlstra <peterz@...radead.org>
Cc: LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
"Paul E. McKenney" <paulmck@...nel.org>,
Andy Lutomirski <luto@...nel.org>,
Alexandre Chartre <alexandre.chartre@...cle.com>,
Frederic Weisbecker <frederic@...nel.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Sean Christopherson <sean.j.christopherson@...el.com>,
Masami Hiramatsu <mhiramat@...nel.org>,
Petr Mladek <pmladek@...e.com>,
Steven Rostedt <rostedt@...dmis.org>,
Joel Fernandes <joel@...lfernandes.org>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Juergen Gross <jgross@...e.com>,
Brian Gerst <brgerst@...il.com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Will Deacon <will@...nel.org>,
Tom Lendacky <thomas.lendacky@....com>,
Wei Liu <wei.liu@...nel.org>,
Michael Kelley <mikelley@...rosoft.com>,
Jason Chen CJ <jason.cj.chen@...el.com>,
Zhao Yakui <yakui.zhao@...el.com>
Subject: Re: [patch V6 01/37] tracing/hwlat: Use ktime_get_mono_fast_ns()
Peter Zijlstra <peterz@...radead.org> writes:
> On Sat, May 16, 2020 at 01:45:48AM +0200, Thomas Gleixner wrote:
>> Timestamping in the hardware latency detector uses sched_clock() underneath
>> and depends on CONFIG_GENERIC_SCHED_CLOCK=n because sched clocks from that
>> subsystem are not NMI safe.
>
> AFAICT that's not actually true, see commit:
>
> 1809bfa44e10 ("timers, sched/clock: Avoid deadlock during read from NMI")
>
> that said, no objection to switching to ktime, people that run HPET
> clocks deserve all the pain and suffering available with those setups.
Correct ...
Powered by blists - more mailing lists