History

tracing/fastboot: use sched switch tracer from boot tracer

Impact: enhance boot trace output with scheduling events Use the sched_switch tracer from the boot tracer. We also can trace schedule events inside the initcalls. Sched tracing is disabled after the initcall has finished and then reenabled before the next one is started.

Frederic Weisbecker committed 18 years ago

Commit d7ad44b1 parent e55f6054 files · +12 −3Browse files

Showing the changes to kernel/trace/trace_boot.c (1 of 4 files). Show all

Unified · Split

kernel/trace/trace_boot.c+6−0
@@ -27,10 +27,14 @@ void start_boot_trace(void) · 26 unmodified lines
2727
2828 void enable_boot_trace(void)
2929 {
30+ if (pre_initcalls_finished)
31+ tracing_start_cmdline_record();
3032 }
3133
3234 void disable_boot_trace(void)
3335 {
36+ if (pre_initcalls_finished)
37+ tracing_stop_cmdline_record();
3438 }
3539
3640 void reset_boot_trace(struct trace_array *tr)
@@ -45,6 +49,8 @@ static void boot_trace_init(struct trace_array *tr) · 8 unmodified lines
4549
4650 for_each_cpu_mask(cpu, cpu_possible_map)
4751 tracing_reset(tr, cpu);
52+
53+ sched_switch_trace.init(tr);
4854 }
4955
5056 static void boot_trace_ctrl_update(struct trace_array *tr)

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t