Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • I ipipe-x86
  • Project information
    • Project information
    • Activity
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • xenomai
  • ipipe-x86
  • Repository

Switch branch/tag
  • ipipe-x86
  • kernel
  • trace
  • trace.c
Find file BlameHistoryPermalink
  • Steven Rostedt's avatar
    tracing: make trace pipe recognize latency format flag · 112f38a7
    Steven Rostedt authored Jun 01, 2009
    
    
    The trace_pipe did not recognize the latency format flag and would produce
    different output than the trace file. The problem was partly due that
    the trace flags in the iterator was not set as well as the trace_pipe
    zeros out part of the iterator (including the flags) to be able to use
    the same routines as the trace file. trace_flags of the iterator should
    not cause any problems when not zeroed out by for trace_pipe.
    Reported-by: default avatarJohannes Berg <johannes@sipsolutions.net>
    Signed-off-by: default avatarSteven Rostedt <rostedt@goodmis.org>
    112f38a7

Replace trace.c

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.

Imprint & Privacy Policy