Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • linux
  • Repository
You need to sign in or sign up before continuing.
  • linux
  • kernel
  • trace
  • ring_buffer.c
Find file BlameHistoryPermalink
  • Steven Rostedt (VMware)'s avatar
    ring-buffer: Have ring_buffer_empty() not depend on tracing stopped · ead6ecfd
    Steven Rostedt (VMware) authored Mar 17, 2020
    It was complained about that when the trace file is read, that the tracing
    is disabled, as the iterator expects writing to the buffer it reads is not
    updated. Several steps are needed to make the iterator handle a writer,
    by testing if things have changed as it reads.
    
    This step is to make ring_buffer_empty() expect the buffer to be changing.
    Note if the current location of the iterator is overwritten, then it will
    return false as new data is being added. Note, that this means that data
    will be skipped.
    
    Link: http://lkml.kernel.org/r/20200317213415.870741809@goodmis.org
    
    
    
    Signed-off-by: default avatarSteven Rostedt (VMware) <rostedt@goodmis.org>
    ead6ecfd
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7