Re: [PATCH V2] time/sched_clock: mark sched_clock_read_begin/retry as notrace

2020-09-29 Thread Quanyang Wang
Hi Peter, On 9/29/20 3:49 PM, Peter Zijlstra wrote: On Tue, Sep 29, 2020 at 09:50:51AM +0800, quanyang.w...@windriver.com wrote: From: Quanyang Wang Since sched_clock_read_begin and sched_clock_read_retry are called by notrace function sched_clock, they shouldn't be traceable either, or else

Re: [PATCH V2] time/sched_clock: mark sched_clock_read_begin/retry as notrace

2020-09-29 Thread Peter Zijlstra
On Tue, Sep 29, 2020 at 09:50:51AM +0800, quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Since sched_clock_read_begin and sched_clock_read_retry are called > by notrace function sched_clock, they shouldn't be traceable either, > or else ftrace_graph_caller will run into a dead loop

[PATCH V2] time/sched_clock: mark sched_clock_read_begin/retry as notrace

2020-09-28 Thread quanyang.wang
From: Quanyang Wang Since sched_clock_read_begin and sched_clock_read_retry are called by notrace function sched_clock, they shouldn't be traceable either, or else ftrace_graph_caller will run into a dead loop on the path as below (arm for instance): ftrace_graph_caller prepare_ftrace_retu