Context Navigation

Changes between Version 19 and Version 20 of RTSsummaryEvents

v19	v20
8	8	Here is a [https://github.com/Mikolaj/ThreadScope/raw/working/SummaryPanelMockup.png screenshot]
9	9	of what we can already do using the current set of events. It happens we can do as much for the whole runtime
10		as for the time intervals in this case. The first line of +RTS -s follows.
	10	as for the time intervals in this case.
	11
	12	The first line of +RTS -s follows.
11	13
12	14	{{{
…	…
46	48	}}}
47	49
48		No idea~~. Ask JaffaCake what the following formula~~ means:
	50	No idea what new events we need to calculate fragmentation. Ask JaffaCake what the following formula from the RTS -s code means:
49	51
50	52	{{{
…	…
60	62	}}}
61	63
62		Ask JaffaCake if RequestParGC is enough to tell seq/par and why some StartGC
63		follow neither RequestParGC nor RequestSeqGC (on the same capability, at least).
64		Split the current GC events into generations and into seq/par
	64	Ask JaffaCake if RequestParGC is enough to distinguish between seq and par GC and why some StartGC
	65	follow neither RequestParGC nor RequestSeqGC (on the same capability, at least, assuming I tested it right).
	66
	67	We'd need to split the current GC events into generations and into seq/par
65	68	(if RequestParGC is not enough to tell seq/par). Note that we don't want
66	69	to report the CPU time, only the elapsed time, and that's fine.