Abstract over the way eventlogs are flushed
Currently eventlog data is always written to a file `progname.eventlog`. This patch introduces the `flushEventLog` field in `RtsConfig` which allows to customize the writing of eventlog data. One possible scenario is the ongoing live-profile-monitor effort by @NCrashed which slurps all eventlog data through `fluchEventLog`. `flushEventLog` takes a buffer with eventlog data and its size and returns `false` (0) in case eventlog data could not be procesed. Reviewers: simonmar, austin, erikd, bgamari Reviewed By: simonmar, bgamari Subscribers: qnikst, thomie, NCrashed Differential Revision: https://phabricator.haskell.org/D2934
Showing
- docs/users_guide/8.2.1-notes.rst 4 additions, 0 deletionsdocs/users_guide/8.2.1-notes.rst
- docs/users_guide/runtime_control.rst 39 additions, 4 deletionsdocs/users_guide/runtime_control.rst
- includes/RtsAPI.h 4 additions, 0 deletionsincludes/RtsAPI.h
- includes/rts/EventLogWriter.h 40 additions, 0 deletionsincludes/rts/EventLogWriter.h
- rts/RtsFlags.c 1 addition, 0 deletionsrts/RtsFlags.c
- rts/Trace.c 18 additions, 3 deletionsrts/Trace.c
- rts/eventlog/EventLog.c 51 additions, 77 deletionsrts/eventlog/EventLog.c
- rts/eventlog/EventLog.h 2 additions, 1 deletionrts/eventlog/EventLog.h
- rts/eventlog/EventLogWriter.c 122 additions, 0 deletionsrts/eventlog/EventLogWriter.c
Loading
Please register or sign in to comment