Re: [PATCH 3.19-rc2 v14 0/7] arm: Implement arch_trigger_all_cpu_backtrace

2015-01-22 Thread Daniel Thompson
On 21/01/15 13:48, Daniel Thompson wrote: > On 21/01/15 13:06, Steven Rostedt wrote: >> On Wed, 21 Jan 2015 10:47:37 + >> Daniel Thompson wrote: >> >> With this patchset, is it possible to call sched_clock() from within NMI context? I ask because the generic sched_clock() code is

Re: [PATCH 3.19-rc2 v14 0/7] arm: Implement arch_trigger_all_cpu_backtrace

2015-01-22 Thread Daniel Thompson
On 21/01/15 13:48, Daniel Thompson wrote: On 21/01/15 13:06, Steven Rostedt wrote: On Wed, 21 Jan 2015 10:47:37 + Daniel Thompson daniel.thomp...@linaro.org wrote: With this patchset, is it possible to call sched_clock() from within NMI context? I ask because the generic sched_clock()

Re: [PATCH 3.19-rc2 v14 0/7] arm: Implement arch_trigger_all_cpu_backtrace

2015-01-21 Thread Daniel Thompson
On 21/01/15 13:06, Steven Rostedt wrote: > On Wed, 21 Jan 2015 10:47:37 + > Daniel Thompson wrote: > > >>> With this patchset, is it possible to call sched_clock() from within NMI >>> context? I ask because the generic sched_clock() code is not NMI safe > > That's not good. Better not run

Re: [PATCH 3.19-rc2 v14 0/7] arm: Implement arch_trigger_all_cpu_backtrace

2015-01-21 Thread Steven Rostedt
On Wed, 21 Jan 2015 10:47:37 + Daniel Thompson wrote: > > With this patchset, is it possible to call sched_clock() from within NMI > > context? I ask because the generic sched_clock() code is not NMI safe That's not good. Better not run function tracing, as that could trace functions in

Re: [PATCH 3.19-rc2 v14 0/7] arm: Implement arch_trigger_all_cpu_backtrace

2015-01-21 Thread Daniel Thompson
On 20/01/15 20:53, Stephen Boyd wrote: > On 01/20/2015 02:25 AM, Daniel Thompson wrote: >> On 13/01/15 10:26, Daniel Thompson wrote: >>> Hi Thomas, Hi Jason: >>> Patches 1 to 3 are for you (and should be separable from the rest >>> of the series). The patches haven't changes since the last

Re: [PATCH 3.19-rc2 v14 0/7] arm: Implement arch_trigger_all_cpu_backtrace

2015-01-21 Thread Daniel Thompson
On 20/01/15 20:53, Stephen Boyd wrote: On 01/20/2015 02:25 AM, Daniel Thompson wrote: On 13/01/15 10:26, Daniel Thompson wrote: Hi Thomas, Hi Jason: Patches 1 to 3 are for you (and should be separable from the rest of the series). The patches haven't changes since the last time I

Re: [PATCH 3.19-rc2 v14 0/7] arm: Implement arch_trigger_all_cpu_backtrace

2015-01-21 Thread Steven Rostedt
On Wed, 21 Jan 2015 10:47:37 + Daniel Thompson daniel.thomp...@linaro.org wrote: With this patchset, is it possible to call sched_clock() from within NMI context? I ask because the generic sched_clock() code is not NMI safe That's not good. Better not run function tracing, as that could

Re: [PATCH 3.19-rc2 v14 0/7] arm: Implement arch_trigger_all_cpu_backtrace

2015-01-21 Thread Daniel Thompson
On 21/01/15 13:06, Steven Rostedt wrote: On Wed, 21 Jan 2015 10:47:37 + Daniel Thompson daniel.thomp...@linaro.org wrote: With this patchset, is it possible to call sched_clock() from within NMI context? I ask because the generic sched_clock() code is not NMI safe That's not good.

Re: [PATCH 3.19-rc2 v14 0/7] arm: Implement arch_trigger_all_cpu_backtrace

2015-01-20 Thread Stephen Boyd
On 01/20/2015 02:25 AM, Daniel Thompson wrote: > On 13/01/15 10:26, Daniel Thompson wrote: >> Hi Thomas, Hi Jason: >> Patches 1 to 3 are for you (and should be separable from the rest >> of the series). The patches haven't changes since the last time >> I posted them. The changes in

Re: [PATCH 3.19-rc2 v14 0/7] arm: Implement arch_trigger_all_cpu_backtrace

2015-01-20 Thread Daniel Thompson
On 13/01/15 10:26, Daniel Thompson wrote: > Hi Thomas, Hi Jason: > Patches 1 to 3 are for you (and should be separable from the rest > of the series). The patches haven't changes since the last time > I posted them. The changes in v14 tidy up the later part of the > patch set in

Re: [PATCH 3.19-rc2 v14 0/7] arm: Implement arch_trigger_all_cpu_backtrace

2015-01-20 Thread Daniel Thompson
On 13/01/15 10:26, Daniel Thompson wrote: Hi Thomas, Hi Jason: Patches 1 to 3 are for you (and should be separable from the rest of the series). The patches haven't changes since the last time I posted them. The changes in v14 tidy up the later part of the patch set in order

Re: [PATCH 3.19-rc2 v14 0/7] arm: Implement arch_trigger_all_cpu_backtrace

2015-01-20 Thread Stephen Boyd
On 01/20/2015 02:25 AM, Daniel Thompson wrote: On 13/01/15 10:26, Daniel Thompson wrote: Hi Thomas, Hi Jason: Patches 1 to 3 are for you (and should be separable from the rest of the series). The patches haven't changes since the last time I posted them. The changes in v14 tidy up

[PATCH 3.19-rc2 v14 0/7] arm: Implement arch_trigger_all_cpu_backtrace

2015-01-13 Thread Daniel Thompson
Hi Thomas, Hi Jason: Patches 1 to 3 are for you (and should be separable from the rest of the series). The patches haven't changes since the last time I posted them. The changes in v14 tidy up the later part of the patch set in order to share more code between x86 and arm. This

[PATCH 3.19-rc2 v14 0/7] arm: Implement arch_trigger_all_cpu_backtrace

2015-01-13 Thread Daniel Thompson
Hi Thomas, Hi Jason: Patches 1 to 3 are for you (and should be separable from the rest of the series). The patches haven't changes since the last time I posted them. The changes in v14 tidy up the later part of the patch set in order to share more code between x86 and arm. This