summaryrefslogtreecommitdiff
path: root/rts/eventlog
Commit message (Collapse)AuthorAgeFilesLines
* Add EVENT_CREATE_SPARK_THREAD to replace EVENT_SPARK_TO_THREADSimon Marlow2009-04-231-16/+12
| | | | Also some tidyups and renaming
* Removed unused function postEventTypeID.donnie@darthik.com2009-04-131-3/+0
| | | | | postEventTypeID was used to post event marker IDs, but instead we just call postWord16 directly; thus, this function is unused.
* Added new EventLog event: Spark to Thread.donnie@darthik.com2009-04-131-1/+14
|
* Changed postEvent last argument from "nat from" to "StgWord64 other".donnie@darthik.com2009-04-132-5/+5
| | | | | | | StgWord64 other better represents this argument since it can be used as any particular data, thus "other" and not the "from" capability as it was previously strictly used. Also, StgWord64 is normally larger than type nat to allow for larger data to be passed through the "other" argument.
* Fixed ThreadID to be defined as StgThreadID, not StgWord64. Changed ↵donnie@darthik.com2009-04-131-11/+16
| | | | | | | | | | CapabilityNum to CapNo. Added helper functions postCapNo() and postThreadID(). ThreadID was StgWord64, but should have been StgThreadID, which is currently StgWord32. Changed name from CapabilityNum to CapNo to better reflect naming in Capability struct where "no" is the capability number. Modified EventLog.c to use the helper functions postCapNo() and postThreadID () for CapNo and ThreadID.
* Fixed error in order of EventTypeDescriptions -- seq and par GC come after ↵donnie@darthik.com2009-04-031-2/+2
| | | | | | | | start and finish GC. EventTypeDescriptions order must be synchronized with the event type definitions in includes/EventLogFormat.h for the definitions to correctly index with the matching description.
* Eventlog support for new event type: create spark.donnie@darthik.com2009-04-031-1/+4
|
* Fix warnings with older versions of gcc (3.4.5)Simon Marlow2009-03-191-55/+44
|
* Add fast event loggingSimon Marlow2009-03-172-0/+519
Generate binary log files from the RTS containing a log of runtime events with timestamps. The log file can be visualised in various ways, for investigating runtime behaviour and debugging performance problems. See for example the forthcoming ThreadScope viewer. New GHC option: -eventlog (link-time option) Enables event logging. +RTS -l (runtime option) Generates <prog>.eventlog with the binary event information. This replaces some of the tracing machinery we already had in the RTS: e.g. +RTS -vg for GC tracing (we should do this using the new event logging instead). Event logging has almost no runtime cost when it isn't enabled, though in the future we might add more fine-grained events and this might change; hence having a link-time option and compiling a separate version of the RTS for event logging. There's a small runtime cost for enabling event-logging, for most programs it shouldn't make much difference. (Todo: docs)
View Lorry Controller Status