Skip to content

Add eventlog events for `-p` profiling

The summary provided by -p profiling doesn't give an extremely accurate picture of the execution of a program. You can see generally how long something takes but you don't know what time it was called.

If we want to use tools like speedscope the information needs to be more fine grained.

I can think of two potential options.

  1. On each tick dump the current call stack to the eventlog (easy)
  2. Log an event each time a cost centre is entered (more overhead)

Implementation notes:

  1. Modifying Proftimer.handleProfTick
  2. Modifying ENTER_CCS_THUNK (perhaps)?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information