| | 28 | `gc-start (cap)`:: |
| | 29 | The specified capability gets ready for a garbage collection. |
| | 30 | `gc-end (cap)`:: |
| | 31 | The specified capability completed a garbage collection. |
| | 32 | `gc-request-seq-gc (cap)`:: |
| | 33 | We are about to perform a single-threaded garbage collection (meaning that we will grab all capabilities, and then, perform the GC on the specified capability). |
| | 34 | `gc-request-par-gc (cap)`:: |
| | 35 | We are about to perform a parallel garbage collection (this still means all mutator threads need to stop). We might need to wait for the other capabilities to donate a worker thread each. |
| | 36 | `create-spark-thread (cap, tid)`:: |
| | 37 | We just turned a spark into the specified thread on the given capability. |
| | 38 | `startup (num_caps)`:: |
| | 39 | Initialising the runtime system with the given number of capabilities (that's the value passed with `+RTS -N`). |
| | 40 | `user-msg (cap, msg)`:: |
| | 41 | The given user message (a string that you need to copy with `copyinstr()`) was emitted on the given capability; this happens when a call to `traceEvent` is being made, passing the message as an argument. |
