Re: [RFC PATCH 06/20] coresight: etm3x: unlocking tracer in default arch init

2015-10-02 Thread Mathieu Poirier
On 1 October 2015 at 22:47, Alexander Shishkin wrote: > Mathieu Poirier writes: > >> On 30 September 2015 at 05:33, Alexander Shishkin >> wrote: >>> Mathieu Poirier writes: >>> Calling function 'smp_call_function_single()' to unlock the tracer and calling it right after to perform the

Re: [RFC PATCH 06/20] coresight: etm3x: unlocking tracer in default arch init

2015-10-01 Thread Alexander Shishkin
Mathieu Poirier writes: > On 30 September 2015 at 05:33, Alexander Shishkin > wrote: >> Mathieu Poirier writes: >> >>> Calling function 'smp_call_function_single()' to unlock the >>> tracer and calling it right after to perform the default >>> initialisation doesn't make sense. >>> >>> Moving '

Re: [RFC PATCH 06/20] coresight: etm3x: unlocking tracer in default arch init

2015-10-01 Thread Mathieu Poirier
On 30 September 2015 at 05:33, Alexander Shishkin wrote: > Mathieu Poirier writes: > >> Calling function 'smp_call_function_single()' to unlock the >> tracer and calling it right after to perform the default >> initialisation doesn't make sense. >> >> Moving 'etm_os_unlock()' just before making t

Re: [RFC PATCH 06/20] coresight: etm3x: unlocking tracer in default arch init

2015-09-30 Thread Alexander Shishkin
Mathieu Poirier writes: > Calling function 'smp_call_function_single()' to unlock the > tracer and calling it right after to perform the default > initialisation doesn't make sense. > > Moving 'etm_os_unlock()' just before making the default > initialisation results in the same outcome while savi

[RFC PATCH 06/20] coresight: etm3x: unlocking tracer in default arch init

2015-09-18 Thread Mathieu Poirier
Calling function 'smp_call_function_single()' to unlock the tracer and calling it right after to perform the default initialisation doesn't make sense. Moving 'etm_os_unlock()' just before making the default initialisation results in the same outcome while saving one call to 'smp_call_function_sin