Re: [PATCH 1/2] tracing: fix uptime overflow problem

On Sat, 28 Jun 2014 19:10:00 +0800 Xie XiuQi wrote: > /* > - * trace_jiffy_clock(): Simply use jiffies as a clock counter. > + * trace_clock_uptime(): Use lockless version __current_kernel_time, > + * so it's safe in NMI context. > */ > -u64 notrace trace_clock_jiffies(void) > +u64 notrace

Re: [PATCH 1/2] tracing: fix uptime overflow problem

On Sat, 28 Jun 2014 19:10:00 +0800 Xie XiuQi xiexi...@huawei.com wrote: /* - * trace_jiffy_clock(): Simply use jiffies as a clock counter. + * trace_clock_uptime(): Use lockless version __current_kernel_time, + * so it's safe in NMI context. */ -u64 notrace trace_clock_jiffies(void)

[PATCH 1/2] tracing: fix uptime overflow problem

The "uptime" tracer added in: commit 8aacf017b065a805d27467843490c976835eb4a5 tracing: Add "uptime" trace clock that uses jiffies has wraparound problems when the system has been up more than 1 hour 11 minutes and 34 seconds. It converts jiffies to nanoseconds using:

[PATCH 1/2] tracing: fix uptime overflow problem

The uptime tracer added in: commit 8aacf017b065a805d27467843490c976835eb4a5 tracing: Add uptime trace clock that uses jiffies has wraparound problems when the system has been up more than 1 hour 11 minutes and 34 seconds. It converts jiffies to nanoseconds using: