summaryrefslogtreecommitdiff
path: root/docs/users_guide/eventlog-formats.rst
blob: af172758bfed52f5001b9d5cdca3ec0ad5da4ea6 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
.. _eventlog-encodings:

Eventlog encodings
==================

This section documents the encodings of the events emitted to GHC's
:ref:`event log <rts-eventlog>`. These events can include information about the
thread scheduling events, garbage collection statistics, profiling information,
user-defined tracing events.

This section is intended for implementors of tooling which consume these events.
GHC ships with a C header file (``EventlogFormat.h``) which provides symbolic
names for the event type IDs described in this file.


Event log format
----------------

The log format is designed to be extensible: old tools should be
able to parse (but not necessarily understand all of) new versions
of the format, and new tools will be able to understand old log
files.

- The format is endian-independent: all values are represented in
  big-endian order.

- The format is extensible:

  - The header describes each event type and its length.  Tools
    that don't recognise a particular event type can skip those events.

  - There is room for extra information in the event type
    specification, which can be ignored by older tools.

  - Events can have extra information added, but existing fields
    cannot be changed.  Tools should ignore extra fields at the
    end of the event record.

The event-log stream begins with a header describing the event types present in
the file. The header is followed by the event records themselves, each of which
consist of a 64-bit timestamp

.. code-block:: none

    log : EVENT_HEADER_BEGIN
          EventType*
          EVENT_HEADER_END
          EVENT_DATA_BEGIN
          Event*
          EVENT_DATA_END

    EventType :
          EVENT_ET_BEGIN
          Word16         -- unique identifier for this event
          Int16          -- >=0  size of the event in bytes (minus the header)
                         -- -1   variable size
          Word32         -- length of the next field in bytes
          Word8*         -- string describing the event
          Word32         -- length of the next field in bytes
          Word8*         -- extra info (for future extensions)
          EVENT_ET_END

    Event :
          Word16         -- event_type
          Word64         -- time (nanosecs)
          [Word16]       -- length of the rest (for variable-sized events only)
          ... extra event-specific info ...

There are two classes of event types:

 - *Fixed size*: All event records of a fixed-sized type are of the same
   length, given in the header event-log header.

 - *Variable size*: Each event record includes a length field.

Runtime system diagnostics
--------------------------

 * ``ThreadId ~ Word32``
 * ``CapNo ~ Word16``
 * ``CapSetId ~ Word32``

Capability sets
~~~~~~~~~~~~~~~

TODO

Environment information
~~~~~~~~~~~~~~~~~~~~~~~

These events are typically produced during program startup and describe the
environment which the program is being run in.

.. event-type:: RTS_IDENTIFIER

   :tag: 29
   :length: variable
   :field CapSetId: Capability set
   :field String: Runtime system name and version.

   Describes the name and version of the runtime system responsible for the
   indicated capability set.

.. event-type:: PROGRAM_ARGS

   :tag: 30
   :length: variable
   :field CapSetId: Capability set
   :field [String]: The command-line arguments passed to the program

   Describes the command-line used to start the program.

.. event-type:: PROGRAM_ENV

   :tag: 31
   :length: variable
   :field CapSetId: Capability set
   :field [String]: The environment variable name/value pairs. (TODO: encoding?)

   Describes the environment variables present in the program's environment.

Thread and scheduling events
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

.. event-type:: CREATE_THREAD

   :tag: 0
   :length: fixed
   :field ThreadId: thread id

   Marks the creation of a Haskell thread.


.. event-type:: RUN_THREAD

   :tag: 1
   :length: fixed
   :field ThreadId: thread id

   The indicated thread has started running.


.. event-type:: STOP_THREAD

   :tag: 2
   :length: fixed
   :field ThreadId: thread id
   :field Word16: status

      * 1: HeapOverflow
      * 2: StackOverflow
      * 3: ThreadYielding
      * 4: ThreadBlocked
      * 5: ThreadFinished
      * 6: ForeignCall
      * 7: BlockedOnMVar
      * 8: BlockedOnBlackHole
      * 9: BlockedOnRead
      * 10: BlockedOnWrite
      * 11: BlockedOnDelay
      * 12: BlockedOnSTM
      * 13: BlockedOnDoProc
      * 16: BlockedOnMsgThrowTo

   :field ThreadId: thread id of thread being blocked on (only for some status
                    values)

   The indicated thread has stopped running for the reason given by ``status``.


.. event-type:: THREAD_RUNNABLE

   :tag: 3
   :length: fixed
   :field ThreadId: thread id

   The indicated thread is has been marked as ready to run.


.. event-type:: MIGRATE_THREAD

   :tag: 4
   :length: fixed
   :field ThreadId: thread id
   :field CapNo: capability

   The indicated thread has been migrated to a new capability.


.. event-type:: THREAD_WAKEUP

   :tag: 8
   :length: fixed
   :field ThreadId: thread id
   :field CapNo: other capability

   The indicated thread has been woken up on another capability.

.. event-type:: THREAD_LABEL

   :tag: 44
   :length: fixed
   :field ThreadId: thread id
   :field String: label

   The indicated thread has been given a label (e.g. with
   :base-ref:`Control.Concurrent.setThreadLabel`).


Garbage collector events
~~~~~~~~~~~~~~~~~~~~~~~~

.. event-type:: GC_START

   :tag: 9
   :length: fixed

   A garbage collection pass has been started.

.. event-type:: GC_END

   :tag: 10
   :length: fixed

   A garbage collection pass has been finished.

.. event-type:: REQUEST_SEQ_GC

   :tag: 11
   :length: fixed

   A sequential garbage collection has been requested by a capability.

.. event-type:: REQUEST_PAR_GC

   :tag: 12
   :length: fixed

   A parallel garbage collection has been requested by a capability.

.. event-type:: GC_IDLE

   :tag: 20
   :length: fixed

   An idle-time garbage collection has been started.

.. event-type:: GC_WORK

   :tag: 21
   :length: fixed

   Marks the start of concurrent scavenging.

.. event-type:: GC_DONE

   :tag: 22
   :length: fixed

   Marks the end of concurrent scavenging.

.. event-type:: GC_STATS_GHC

   :tag: 53
   :length: fixed
   :field CapSetId: heap capability set
   :field Word16: generation of collection
   :field Word64: bytes copied
   :field Word64: bytes of slop found
   :field Word64: TODO
   :field Word64: number of parallel garbage collection threads
   :field Word64: maximum number of bytes copied by any single collector thread
   :field Word64: total bytes copied by all collector threads

   Report various information about the heap configuration. Typically produced
   during RTS initialization..

.. event-type:: GC_GLOBAL_SYNC

   :tag: 54
   :length: fixed

   TODO

Heap events and statistics
~~~~~~~~~~~~~~~~~~~~~~~~~~

.. event-type:: HEAP_ALLOCATED

   :tag: 49
   :length: fixed
   :field CapSetId: heap capability set
   :field Word64: allocated bytes

   A new chunk of heap has been allocated by the indicated capability set.

.. event-type:: HEAP_SIZE

   :tag: 50
   :length: fixed
   :field CapSetId: heap capability set
   :field Word64: heap size in bytes

   Report the heap size.

.. event-type:: HEAP_LIVE

   :tag: 51
   :length: fixed
   :field CapSetId: heap capability set
   :field Word64: heap size in bytes

   Report the live heap size.

.. event-type:: HEAP_INFO_GHC

   :tag: 52
   :length: fixed
   :field CapSetId: heap capability set
   :field Word16: number of garbage collection generations
   :field Word64: maximum heap size
   :field Word64: allocation area size
   :field Word64: MBlock size
   :field Word64: Block size

   Report various information about the heap configuration. Typically produced
   during RTS initialization..

Spark events
~~~~~~~~~~~~

.. event-type:: CREATE_SPARK_THREAD

   :tag: 15
   :length: fixed

   A thread has been created to perform spark evaluation.

.. event-type:: SPARK_COUNTERS

   :tag: 34
   :length: fixed

   A periodic reporting of various statistics of spark evaluation.

.. event-type:: SPARK_CREATE

   :tag: 35
   :length: fixed

   A spark has been added to the spark pool.

.. event-type:: SPARK_DUD

   :tag: 36
   :length: fixed

   TODO

.. event-type:: SPARK_OVERFLOW

   :tag: 37
   :length: fixed

   TODO

.. event-type:: SPARK_RUN

   :tag: 38
   :length: fixed

   Evaluation has started on a spark.

.. event-type:: SPARK_STEAL

   :tag: 39
   :length: fixed
   :field Word16: capability from which the spark was stolen

   A spark has been stolen from another capability for evaluation.

.. event-type:: SPARK_FIZZLE

   :tag: 40
   :length: fixed

   A spark has been GC'd before being evaluated.

.. event-type:: SPARK_GC

   :tag: 41
   :length: fixed

   An unevaluated spark has been garbage collected.

Capability events
~~~~~~~~~~~~~~~~~

.. event-type:: CAP_CREATE

   :tag: 45
   :length: fixed
   :field CapNo: the capability number

   A capability has been started.

.. event-type:: CAP_DELETE

   :tag: 46
   :length: fixed

   A capability has been deleted.

.. event-type:: CAP_DISABLE

   :tag: 47
   :length: fixed

   A capability has been disabled.

.. event-type:: CAP_ENABLE

   :tag: 48
   :length: fixed

   A capability has been enabled.

Task events
~~~~~~~~~~~

.. event-type:: TASK_CREATE

   :tag: 55
   :length: fixed
   :field TaskId: task id
   :field CapNo: capability number
   :field ThreadId: TODO

   Marks the creation of a task.

.. event-type:: TASK_MIGRATE

   :tag: 56
   :length: fixed
   :field TaskId: task id
   :field CapNo: old capability
   :field CapNo: new capability

   Marks the migration of a task to a new capability.

Tracing events
~~~~~~~~~~~~~~

.. event-type:: LOG_MSG

   :tag: 16
   :length: variable
   :field String: The message

   A log message from the runtime system.

.. event-type:: BLOCK_MARKER

   :tag: 18
   :length: variable
   :field Word32: size
   :field Word64: end time in nanoseconds
   :field String: marker name

   TODO

.. event-type:: USER_MSG

   :tag: 19
   :length: variable
   :field String: message

   A user log message (from, e.g., :base-ref:`Control.Concurrent.traceEvent`).

.. event-type:: USER_MARKER

   :tag: 58
   :length: variable
   :field String: marker name

   A user marker (from :base-ref:`Debug.Trace.traceMarker`).


.. _heap-profiler-events:

Heap profiler event log output
------------------------------

The heap profiler can produce output to GHC's event log, allowing samples to
be correlated with other event log events over the program's lifecycle.

This section defines the layout of these events. The ``String`` type below is
defined to be a UTF-8 encoded NUL-terminated string.

Metadata event types
~~~~~~~~~~~~~~~~~~~~

Beginning of sample stream
^^^^^^^^^^^^^^^^^^^^^^^^^^

A single fixed-width event emitted during program start-up describing the samples that follow.

.. event-type:: HEAP_PROF_BEGIN

   :tag: 160
   :length: variable
   :field Word8: profile ID
   :field Word64: sampling period in nanoseconds
   :field Word32: sample breadown type. One of,

      * ``HEAP_PROF_BREAKDOWN_COST_CENTER`` (output from :rts-flag:`-hc`)
      * ``HEAP_PROF_BREAKDOWN_CLOSURE_DESCR`` (output from :rts-flag:`-hd`)
      * ``HEAP_PROF_BREAKDOWN_RETAINER`` (output from :rts-flag:`-hr`)
      * ``HEAP_PROF_BREAKDOWN_MODULE`` (output from :rts-flag:`-hm`)
      * ``HEAP_PROF_BREAKDOWN_TYPE_DESCR`` (output from :rts-flag:`-hy`)
      * ``HEAP_PROF_BREAKDOWN_BIOGRAPHY`` (output from :rts-flag:`-hb`)
      * ``HEAP_PROF_BREAKDOWN_CLOSURE_TYPE`` (output from :rts-flag:`-hT`)

   :field String: module filter
   :field String: closure description filter
   :field String: type description filter
   :field String: cost centre filter
   :field String: cost centre stack filter
   :field String: retainer filter
   :field String: biography filter

Cost centre definitions
^^^^^^^^^^^^^^^^^^^^^^^

A variable-length packet produced once for each cost centre,

.. event-type:: HEAP_PROF_COST_CENTRE

   :tag: 161
   :length: fixed
   :field Word32: cost centre number
   :field String: label
   :field String: module
   :field String: source location
   :field Word8: flags:

     * bit 0: is the cost-centre a CAF?


Sample event types
^^^^^^^^^^^^^^^^^^

A sample (consisting of a list of break-down classes, e.g. cost centres, and
heap residency sizes), is to be encoded in the body of one or more events.

We normally mark the beginning of a new sample with an ``EVENT_HEAP_PROF_SAMPLE_BEGIN``
event,

.. event-type:: HEAP_PROF_SAMPLE_BEGIN

   :length: fixed
   :field Word64: sample number

   Marks the beginning of a heap profile sample.

Biographical profiling samples start with the ``EVENT_HEAP_BIO_PROF_SAMPLE_BEGIN``
event. These events also include a timestamp which indicates when the sample
was taken. This is because all these samples will appear at the end of
the eventlog due to how the biographical profiling mode works. You can
use the timestamp to reorder the samples relative to the other events.

.. event-type:: HEAP_BIO_PROF_SAMPLE_BEGIN

   :tag: 166
   :length: fixed
   :field Word64: sample number
   :field Word64: eventlog timestamp in ns

A heap residency census will follow. Since events may only be up to 2^16^ bytes
in length a single sample may need to be split among multiple
``EVENT_HEAP_PROF_SAMPLE`` events. The precise format of the census entries is
determined by the break-down type.

At the end of the sample period the ``EVENT_HEAP_PROF_SAMPLE_END`` event if
emitted. This is useful to properly delimit the sampling period and to record
the total time spent profiling.


.. event-type:: HEAP_PROF_SAMPLE_END

   :tag: 165
   :length: fixed
   :field Word64: sample number

   Marks the end of a heap profile sample.

Cost-centre break-down
^^^^^^^^^^^^^^^^^^^^^^

A variable-length packet encoding a heap profile sample broken down by,
 * cost-centre (:rts-flag:`-hc`)


.. event-type:: HEAP_PROF_SAMPLE_COST_CENTRE

   :tag: 163
   :length: variable
   :field Word8: profile ID
   :field Word64: heap residency in bytes
   :field Word8: stack depth
   :field Word32[]: cost centre stack starting with inner-most (cost centre numbers)


String break-down
^^^^^^^^^^^^^^^^^

A variable-length event encoding a heap sample broken down by,

 * type description (:rts-flag:`-hy`)
 * closure description (:rts-flag:`-hd`)
 * module (:rts-flag:`-hm`)

.. event-type:: HEAP_PROF_SAMPLE_STRING

   :tag: 164
   :length: variable
   :field Word8: profile ID
   :field Word64: heap residency in bytes
   :field String: type or closure description, or module name

.. _time-profiler-events:

Time profiler event log output
------------------------------

The time profiling mode enabled by :rts-flag:`-p` also emits
sample events to the eventlog.  At the start of profiling the
tick interval is emitted to the eventlog and then on each tick
the current cost centre stack is emitted. Together these
enable a user to construct an approximate track of the
executation of their program.

Profile begin event
~~~~~~~~~~~~~~~~~~~

.. event-type:: PROF_BEGIN

   :tag: 168
   :length: fixed
   :field Word64: tick interval, in nanoseconds

   Marks the beginning of a time profile.

Profile sample event
~~~~~~~~~~~~~~~~~~~~

A variable-length packet encoding a profile sample.

.. event-type:: PROF_SAMPLE_COST_CENTRE

   :tag: 167
   :length: variable
   :field Word32: capability
   :field Word64: current profiling tick
   :field Word8: stack depth
   :field Word32[]: cost centre stack starting with inner-most (cost centre numbers)

Biographical profile sample event
---------------------------------

A variable-length packet encoding a profile sample.

.. event-type:: BIO_PROF_SAMPLE_BEGIN

   :tag: 166

   TODO

.. _nonmoving-gc-events:

Non-moving GC event output
--------------------------

These events mark various stages of the
:rts-flag:`non-moving collection <--nonmoving-gc>` lifecycle. These are enabled
with the ``+RTS -lg`` event-set.

.. event-type:: CONC_MARK_BEGIN

   :tag: 200
   :length: fixed

   Marks the beginning of marking by the concurrent collector.

.. event-type:: CONC_MARK_END

   :tag: 201
   :length: fixed

   Marks the end of marking by the concurrent collector.

.. event-type:: CONC_SYNC_BEGIN

   :tag: 202
   :length: fixed

   Marks the beginning of the concurrent garbage collector's
   post-mark synchronization phase.

.. event-type:: CONC_SYNC_END

   :tag: 203
   :length: fixed

   Marks the end of the concurrent garbage collector's
   post-mark synchronization phase.

.. event-type:: CONC_SWEEP_BEGIN

   :tag: 204
   :length: fixed

   Marks the beginning of the concurrent garbage collector's
   sweep phase.

.. event-type:: CONC_SWEEP_END

   :tag: 205
   :length: fixed

   Marks the end of the concurrent garbage collector's
   sweep phase.

.. event-type:: CONC_UPD_REM_SET_FLUSH

   :tag: 206
   :length: fixed

   Marks a capability flushing its local update remembered set
   accumulator.

Non-moving heap census
~~~~~~~~~~~~~~~~~~~~~~

The non-moving heap census events (enabled with the ``+RTS -ln`` event-set) are
intended to provide insight into fragmentation of the non-moving heap.

.. event-type:: NONMOVING_HEAP_CENSUS

   :tag: 207
   :length: fixed
   :field Word8: base-2 logarithm of *blk_sz*.
   :field Word32: number of active segments.
   :field Word32: number of filled segments.
   :field Word32: number of live blocks.

   Describes the occupancy of the *blk_sz* sub-heap.

Ticky counters
~~~~~~~~~~~~~~

Programs compiled with :ghc-flag:`-ticky` and :ghc-flag:`-eventlog` and invoked
with ``+RTS -lT`` will emit periodic samples of the ticky entry counters to the
eventlog.

.. event-type:: TICKY_COUNTER_DEF

   :tag: 210
   :length: variable
   :field Word64: counter ID
   :field Word16: arity/field count
   :field String: argument kinds. This is the same as the synonymous field in the
     textual ticky summary.
   :field String: counter name

   Defines a ticky counter.

.. event-type:: TICKY_COUNTER_SAMPLE

   :tag: 211
   :length: fixed
   :field Word64: counter ID
   :field Word64: number of times closures of this type has been entered.
   :field Word64: number of allocations (words)
   :field Word64: number of times this has been allocated (words). Only
     produced for modules compiled with :ghc-flag:`-ticky-allocd`.

   Records the counter statistics at a moment in time.