diff options
| author | Jiri Olsa <[email protected]> | 2011-02-18 15:52:19 +0100 |
|---|---|---|
| committer | Steven Rostedt <[email protected]> | 2011-03-10 10:34:47 -0500 |
| commit | 31274d72f01604f4b02d933b4f3cac84d2c201fd (patch) | |
| tree | d85c4bbe7fab3bcc9347de3a7788789fc2aa7c8d /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 722b3c74695377d11d18a52f3da08114d37f3f37 (diff) | |
tracing: Explain about unstable clock on resume with ring buffer warning
The "Delta way too big" warning might appear on a system with a
unstable shed clock right after the system is resumed and tracing
was enabled at time of suspend.
Since it's not realy a bug, and the unstable sched clock is working
fast and reliable otherwise, Steven suggested to keep using the
sched clock in any case and just to make note in the warning itself.
v2 changes:
- added #ifdef CONFIG_HAVE_UNSTABLE_SCHED_CLOCK
Signed-off-by: Jiri Olsa <[email protected]>
LKML-Reference: <[email protected]>
Signed-off-by: Steven Rostedt <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions