summaryrefslogtreecommitdiff
path: root/Documentation/trace
diff options
context:
space:
mode:
authorSteven Rostedt (Red Hat) <rostedt@goodmis.org>2015-09-03 08:57:12 -0400
committerSteven Rostedt <rostedt@goodmis.org>2015-09-03 08:57:12 -0400
commitb7dc42fd79390c074e2bff3b172b585d5c2d80c2 (patch)
tree82ee758c6c9d42b15236e7e6a1b3d3b20b89f94e /Documentation/trace
parentf0a515780393dffbb363e6d1567da46af6f3c5f3 (diff)
ring-buffer: Revert "ring-buffer: Get timestamp after event is allocated"
The commit a4543a2fa9ef31 "ring-buffer: Get timestamp after event is allocated" is needed for some future work. But after adding it, there is a race somewhere that causes the saved timestamp to have a slight shift, and get ahead of the actual timestamp and make it look like time goes backwards. I'm still looking into why this happens, but in the mean time, this is holding up other work to get in. I'm reverting the change for now (which makes the problem go away), and will add it back after I know what is wrong and fix it. Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'Documentation/trace')
0 files changed, 0 insertions, 0 deletions