Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1466456
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2 0/4] tracing: Add Hardware Latency detector tracer |
| Date | 2016-08-19 16:10 +0200 |
| Message-ID | <s7SEF-6Cv-7@gated-at.bofh.it> (permalink) |
| References | <s4GTn-n4-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Aug 10, 2016 at 09:53:56AM -0400, Steven Rostedt wrote: > Changes since v1: > > . Added checks for CONFIG_GENERIC_SCHED_CLOCK, and if that is set, > only nmi_counts will be recorded when an NMI is triggered, but not > the time in NMI, because the generic sched_clock is not NMI safe. > (suggested by Sebastian Andrzej Siewior) So any of the platforms using GENERIC_SCHED_CLOCK _have_ NMIs ? In any case, for those you could probably use ktime_get_mono_fast_ns().
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [PATCH v2 0/4] tracing: Add Hardware Latency detector tracer Peter Zijlstra <peterz@infradead.org> - 2016-08-19 16:10 +0200
Re: [PATCH v2 0/4] tracing: Add Hardware Latency detector tracer Steven Rostedt <rostedt@goodmis.org> - 2016-08-19 17:00 +0200
Re: [PATCH v2 0/4] tracing: Add Hardware Latency detector tracer Peter Zijlstra <peterz@infradead.org> - 2016-08-19 17:10 +0200
Re: [PATCH v2 0/4] tracing: Add Hardware Latency detector tracer John Stultz <john.stultz@linaro.org> - 2016-08-19 18:40 +0200
Re: [PATCH v2 0/4] tracing: Add Hardware Latency detector tracer Thomas Gleixner <tglx@linutronix.de> - 2016-08-23 11:00 +0200
Re: [PATCH v2 0/4] tracing: Add Hardware Latency detector tracer Peter Zijlstra <peterz@infradead.org> - 2016-08-23 11:50 +0200
csiph-web