Re: [PATCH v8 1/4] nmi_backtrace: add more trigger_*_cpu_backtrace() methods

2016-08-22 Thread Petr Mladek
On Fri 2016-08-19 21:54:31, Chris Metcalf wrote: > On 8/18/2016 10:12 AM, Petr Mladek wrote: > >On Tue 2016-08-16 15:50:21, Chris Metcalf wrote: > >>Currently you can only request a backtrace of either all cpus, or > >>all cpus but yourself. It can also be helpful to request a remote >

Re: [PATCH v8 1/4] nmi_backtrace: add more trigger_*_cpu_backtrace() methods

2016-08-22 Thread Petr Mladek
On Fri 2016-08-19 21:54:31, Chris Metcalf wrote: > On 8/18/2016 10:12 AM, Petr Mladek wrote: > >On Tue 2016-08-16 15:50:21, Chris Metcalf wrote: > >>Currently you can only request a backtrace of either all cpus, or > >>all cpus but yourself. It can also be helpful to request a remote >

Re: [PATCH v8 1/4] nmi_backtrace: add more trigger_*_cpu_backtrace() methods

2016-08-20 Thread Chris Metcalf
On 8/18/2016 10:12 AM, Petr Mladek wrote: On Tue 2016-08-16 15:50:21, Chris Metcalf wrote: Currently you can only request a backtrace of either all cpus, or all cpus but yourself. It can also be helpful to request a remote backtrace of a single cpu, and since we want that, the logical

Re: [PATCH v8 1/4] nmi_backtrace: add more trigger_*_cpu_backtrace() methods

2016-08-20 Thread Chris Metcalf
On 8/18/2016 10:12 AM, Petr Mladek wrote: On Tue 2016-08-16 15:50:21, Chris Metcalf wrote: Currently you can only request a backtrace of either all cpus, or all cpus but yourself. It can also be helpful to request a remote backtrace of a single cpu, and since we want that, the logical

Re: [PATCH v8 1/4] nmi_backtrace: add more trigger_*_cpu_backtrace() methods

2016-08-18 Thread Petr Mladek
On Tue 2016-08-16 15:50:21, Chris Metcalf wrote: > Currently you can only request a backtrace of either all cpus, or > all cpus but yourself. It can also be helpful to request a remote > backtrace of a single cpu, and since we want that, the logical > extension is to support a cpumask as the

Re: [PATCH v8 1/4] nmi_backtrace: add more trigger_*_cpu_backtrace() methods

2016-08-18 Thread Petr Mladek
On Tue 2016-08-16 15:50:21, Chris Metcalf wrote: > Currently you can only request a backtrace of either all cpus, or > all cpus but yourself. It can also be helpful to request a remote > backtrace of a single cpu, and since we want that, the logical > extension is to support a cpumask as the

[PATCH v8 1/4] nmi_backtrace: add more trigger_*_cpu_backtrace() methods

2016-08-16 Thread Chris Metcalf
Currently you can only request a backtrace of either all cpus, or all cpus but yourself. It can also be helpful to request a remote backtrace of a single cpu, and since we want that, the logical extension is to support a cpumask as the underlying primitive. This change modifies the existing

[PATCH v8 1/4] nmi_backtrace: add more trigger_*_cpu_backtrace() methods

2016-08-16 Thread Chris Metcalf
Currently you can only request a backtrace of either all cpus, or all cpus but yourself. It can also be helpful to request a remote backtrace of a single cpu, and since we want that, the logical extension is to support a cpumask as the underlying primitive. This change modifies the existing