Re: [PATCH] arm64: use raw_smp_processor_id in stack backtrace dump

2016-02-11 Thread Shi, Yang
On 2/11/2016 2:41 AM, James Morse wrote: Hi! On 10/02/16 18:12, Shi, Yang wrote: On 2/10/2016 4:10 AM, Will Deacon wrote: On Wed, Feb 10, 2016 at 11:52:31AM +, James Morse wrote: On 10/02/16 10:29, Will Deacon wrote: On Tue, Feb 09, 2016 at 01:26:22PM -0800, Yang Shi wrote:

Re: [PATCH] arm64: use raw_smp_processor_id in stack backtrace dump

2016-02-11 Thread James Morse
Hi! On 10/02/16 18:12, Shi, Yang wrote: > On 2/10/2016 4:10 AM, Will Deacon wrote: >> On Wed, Feb 10, 2016 at 11:52:31AM +, James Morse wrote: >>> On 10/02/16 10:29, Will Deacon wrote: On Tue, Feb 09, 2016 at 01:26:22PM -0800, Yang Shi wrote: > dump_backtrace may be called in kthread

Re: [PATCH] arm64: use raw_smp_processor_id in stack backtrace dump

2016-02-11 Thread James Morse
Hi! On 10/02/16 18:12, Shi, Yang wrote: > On 2/10/2016 4:10 AM, Will Deacon wrote: >> On Wed, Feb 10, 2016 at 11:52:31AM +, James Morse wrote: >>> On 10/02/16 10:29, Will Deacon wrote: On Tue, Feb 09, 2016 at 01:26:22PM -0800, Yang Shi wrote: > dump_backtrace may be called in kthread

Re: [PATCH] arm64: use raw_smp_processor_id in stack backtrace dump

2016-02-11 Thread Shi, Yang
On 2/11/2016 2:41 AM, James Morse wrote: Hi! On 10/02/16 18:12, Shi, Yang wrote: On 2/10/2016 4:10 AM, Will Deacon wrote: On Wed, Feb 10, 2016 at 11:52:31AM +, James Morse wrote: On 10/02/16 10:29, Will Deacon wrote: On Tue, Feb 09, 2016 at 01:26:22PM -0800, Yang Shi wrote:

Re: [PATCH] arm64: use raw_smp_processor_id in stack backtrace dump

2016-02-10 Thread Shi, Yang
On 2/10/2016 4:10 AM, Will Deacon wrote: On Wed, Feb 10, 2016 at 11:52:31AM +, James Morse wrote: On 10/02/16 10:29, Will Deacon wrote: On Tue, Feb 09, 2016 at 01:26:22PM -0800, Yang Shi wrote: dump_backtrace may be called in kthread context, which is not bound to a single cpu, i.e.

Re: [PATCH] arm64: use raw_smp_processor_id in stack backtrace dump

2016-02-10 Thread Will Deacon
On Wed, Feb 10, 2016 at 11:52:31AM +, James Morse wrote: > On 10/02/16 10:29, Will Deacon wrote: > > On Tue, Feb 09, 2016 at 01:26:22PM -0800, Yang Shi wrote: > >> dump_backtrace may be called in kthread context, which is not bound to a > >> single > >> cpu, i.e. khungtaskd, then calling

Re: [PATCH] arm64: use raw_smp_processor_id in stack backtrace dump

2016-02-10 Thread James Morse
On 10/02/16 10:29, Will Deacon wrote: > On Tue, Feb 09, 2016 at 01:26:22PM -0800, Yang Shi wrote: >> dump_backtrace may be called in kthread context, which is not bound to a >> single >> cpu, i.e. khungtaskd, then calling smp_processor_id may trigger the below bug >> report: > > If we're

Re: [PATCH] arm64: use raw_smp_processor_id in stack backtrace dump

2016-02-10 Thread Will Deacon
On Tue, Feb 09, 2016 at 01:26:22PM -0800, Yang Shi wrote: > dump_backtrace may be called in kthread context, which is not bound to a > single > cpu, i.e. khungtaskd, then calling smp_processor_id may trigger the below bug > report: If we're preemptible here, it means that our irq_stack_ptr is

Re: [PATCH] arm64: use raw_smp_processor_id in stack backtrace dump

2016-02-10 Thread Shi, Yang
On 2/10/2016 4:10 AM, Will Deacon wrote: On Wed, Feb 10, 2016 at 11:52:31AM +, James Morse wrote: On 10/02/16 10:29, Will Deacon wrote: On Tue, Feb 09, 2016 at 01:26:22PM -0800, Yang Shi wrote: dump_backtrace may be called in kthread context, which is not bound to a single cpu, i.e.

Re: [PATCH] arm64: use raw_smp_processor_id in stack backtrace dump

2016-02-10 Thread Will Deacon
On Tue, Feb 09, 2016 at 01:26:22PM -0800, Yang Shi wrote: > dump_backtrace may be called in kthread context, which is not bound to a > single > cpu, i.e. khungtaskd, then calling smp_processor_id may trigger the below bug > report: If we're preemptible here, it means that our irq_stack_ptr is

Re: [PATCH] arm64: use raw_smp_processor_id in stack backtrace dump

2016-02-10 Thread James Morse
On 10/02/16 10:29, Will Deacon wrote: > On Tue, Feb 09, 2016 at 01:26:22PM -0800, Yang Shi wrote: >> dump_backtrace may be called in kthread context, which is not bound to a >> single >> cpu, i.e. khungtaskd, then calling smp_processor_id may trigger the below bug >> report: > > If we're

Re: [PATCH] arm64: use raw_smp_processor_id in stack backtrace dump

2016-02-10 Thread Will Deacon
On Wed, Feb 10, 2016 at 11:52:31AM +, James Morse wrote: > On 10/02/16 10:29, Will Deacon wrote: > > On Tue, Feb 09, 2016 at 01:26:22PM -0800, Yang Shi wrote: > >> dump_backtrace may be called in kthread context, which is not bound to a > >> single > >> cpu, i.e. khungtaskd, then calling

[PATCH] arm64: use raw_smp_processor_id in stack backtrace dump

2016-02-09 Thread Yang Shi
dump_backtrace may be called in kthread context, which is not bound to a single cpu, i.e. khungtaskd, then calling smp_processor_id may trigger the below bug report: BUG: using smp_processor_id() in preemptible [] code: khungtaskd/71 caller is debug_smp_processor_id+0x1c/0x28 CPU: 3 PID:

[PATCH] arm64: use raw_smp_processor_id in stack backtrace dump

2016-02-09 Thread Yang Shi
dump_backtrace may be called in kthread context, which is not bound to a single cpu, i.e. khungtaskd, then calling smp_processor_id may trigger the below bug report: BUG: using smp_processor_id() in preemptible [] code: khungtaskd/71 caller is debug_smp_processor_id+0x1c/0x28 CPU: 3 PID: