diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2013-12-06 08:34:16 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2013-12-06 08:34:16 -0800 |
| commit | 843f4f4bb1a2c4c196a1af1d18bb6477a580ac78 (patch) | |
| tree | 53b795cb810b7430e46fe485d081bab675792ddb /fs | |
| parent | c537aba00e3f1df8ce6c7c9fcb98b82c0c2d1d2c (diff) | |
| parent | 3ccb01239201af06a07482ec686b14cd148102a5 (diff) | |
Merge tag 'trace-fixes-3.13-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull tracing fix from Steven Rostedt:
"A regression showed up that there's a large delay when enabling all
events. This was prevalent when FTRACE_SELFTEST was enabled which
enables all events several times, and caused the system bootup to
pause for over a minute.
This was tracked down to an addition of a synchronize_sched()
performed when system call tracepoints are unregistered.
The synchronize_sched() is needed between the unregistering of the
system call tracepoint and a deletion of a tracing instance buffer.
But placing the synchronize_sched() in the unreg of *every* system
call tracepoint is a bit overboard. A single synchronize_sched()
before the deletion of the instance is sufficient"
* tag 'trace-fixes-3.13-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
tracing: Only run synchronize_sched() at instance deletion time
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions