summaryrefslogtreecommitdiff
path: root/rts/Trace.c
diff options
context:
space:
mode:
authorMikolaj <mikolaj.konarski@gmail.com>2012-03-09 14:22:06 +0100
committerDuncan Coutts <duncan@well-typed.com>2012-04-04 19:10:45 +0100
commit598109eb0cc2271c33e23b4ddb12123991273f61 (patch)
tree3399a0853bea39cd5ef5e66408ff949937446233 /rts/Trace.c
parent1f809ce6df1dca54b977c6cac8f2b1c745683cf9 (diff)
downloadhaskell-598109eb0cc2271c33e23b4ddb12123991273f61.tar.gz
Fix the timestamps in GC_START and GC_END events on the GC-initiating cap
There was a discrepancy between GC times reported in +RTS -s and the timestamps of GC_START and GC_END events on the cap, on which +RTS -s stats for the given GC are based. This is fixed by posting the events with exactly the same timestamp as generated for the stat calculation. The calls posting the events are moved too, so that the events are emitted close to the time instant they claim to be emitted at. The GC_STATS_GHC was moved, too, ensuring it's emitted before the moved GC_END on all caps, which simplifies tools code.
Diffstat (limited to 'rts/Trace.c')
-rw-r--r--rts/Trace.c13
1 files changed, 13 insertions, 0 deletions
diff --git a/rts/Trace.c b/rts/Trace.c
index f597726f90..995f8a2200 100644
--- a/rts/Trace.c
+++ b/rts/Trace.c
@@ -304,6 +304,19 @@ void traceGcEvent_ (Capability *cap, EventTypeNum tag)
}
}
+void traceGcEventAtT_ (Capability *cap, StgWord64 ts, EventTypeNum tag)
+{
+#ifdef DEBUG
+ if (RtsFlags.TraceFlags.tracing == TRACE_STDERR) {
+ traceGcEvent_stderr(cap, tag);
+ } else
+#endif
+ {
+ /* assuming nullary events and explicitly inserting a timestamp */
+ postEventAtTimestamp(cap, ts, tag);
+ }
+}
+
void traceHeapEvent_ (Capability *cap,
EventTypeNum tag,
CapsetID heap_capset,