On Mon, Jul 09, 2018 at 05:48:54PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt (VMware)
>
> It is unwise to take spin locks from the handlers of trace events.
> Mainly, because they can introduce lockups, because it introduces locks
> in places that are normally not tested. Worse yet,
On Mon, Jul 09, 2018 at 05:48:54PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt (VMware)
>
> It is unwise to take spin locks from the handlers of trace events.
> Mainly, because they can introduce lockups, because it introduces locks
> in places that are normally not tested. Worse yet,
On 2018-07-09 17:48:54 [-0400], Steven Rostedt wrote:
> From: Steven Rostedt (VMware)
>
> Reported-by: Sebastian Andrzej Siewior
Reported-by: Clark Williams
I just forwarded the report.
> Signed-off-by: Steven Rostedt (VMware)
I am in favour of this change.
Sebastian
On 2018-07-09 17:48:54 [-0400], Steven Rostedt wrote:
> From: Steven Rostedt (VMware)
>
> Reported-by: Sebastian Andrzej Siewior
Reported-by: Clark Williams
I just forwarded the report.
> Signed-off-by: Steven Rostedt (VMware)
I am in favour of this change.
Sebastian
From: Steven Rostedt (VMware)
It is unwise to take spin locks from the handlers of trace events.
Mainly, because they can introduce lockups, because it introduces locks
in places that are normally not tested. Worse yet, because trace events
are tucked away in the include/trace/events/ directory,
From: Steven Rostedt (VMware)
It is unwise to take spin locks from the handlers of trace events.
Mainly, because they can introduce lockups, because it introduces locks
in places that are normally not tested. Worse yet, because trace events
are tucked away in the include/trace/events/ directory,
6 matches
Mail list logo