Re: trace: trace_kprobe.c always shows interrupts off

- On Nov 18, 2015, at 1:51 AM, masami hiramatsu pt masami.hiramatsu...@hitachi.com wrote: > Hi Mathieu, Steven, > > From: Steven Rostedt [mailto:rost...@goodmis.org] >> >>On Tue, 17 Nov 2015 16:35:35 + (UTC) >>Mathieu Desnoyers wrote: >> >>> Hi, >>> >>> I notice that trace_kprobe.c

Re: trace: trace_kprobe.c always shows interrupts off

- On Nov 18, 2015, at 1:51 AM, masami hiramatsu pt masami.hiramatsu...@hitachi.com wrote: > Hi Mathieu, Steven, > > From: Steven Rostedt [mailto:rost...@goodmis.org] >> >>On Tue, 17 Nov 2015 16:35:35 + (UTC) >>Mathieu Desnoyers wrote: >> >>> Hi, >>> >>>

RE: trace: trace_kprobe.c always shows interrupts off

Hi Mathieu, Steven, From: Steven Rostedt [mailto:rost...@goodmis.org] > >On Tue, 17 Nov 2015 16:35:35 + (UTC) >Mathieu Desnoyers wrote: > >> Hi, >> >> I notice that trace_kprobe.c does local_save_flags() within >> __kprobe_trace_func(), which is called (at least on x86) with >> interrupts

Re: trace: trace_kprobe.c always shows interrupts off

On Tue, 17 Nov 2015 16:35:35 + (UTC) Mathieu Desnoyers wrote: > Hi, > > I notice that trace_kprobe.c does local_save_flags() within > __kprobe_trace_func(), which is called (at least on x86) with > interrupts always disabled. This is then used as interrupt on/off > state within the recorded

Re: trace: trace_kprobe.c always shows interrupts off

On Tue, 17 Nov 2015 16:35:35 + (UTC) Mathieu Desnoyers wrote: > Hi, > > I notice that trace_kprobe.c does local_save_flags() within > __kprobe_trace_func(), which is called (at least on x86) with > interrupts always disabled. This is then used as interrupt

RE: trace: trace_kprobe.c always shows interrupts off

Hi Mathieu, Steven, From: Steven Rostedt [mailto:rost...@goodmis.org] > >On Tue, 17 Nov 2015 16:35:35 + (UTC) >Mathieu Desnoyers wrote: > >> Hi, >> >> I notice that trace_kprobe.c does local_save_flags() within >> __kprobe_trace_func(), which is called (at