On 4/29/25 12:15, Serhei Makarov wrote:
There is an issue with spontaneous exit of sysprofd (cleanly, with a "Stopping RAPL monitor" message) that I'm trying to understand.
Sysprofd only stays alive as long as it's being used (plus some 30 second timeout or so). So that generally means that something that was using an API crashed/exited and therefore it could exit.
An active RAPL observer _should_ keep sysprofd alive until the client disconnects/stops it.
But sysprof-live-unwinder doesn't necessarily keep sysprofd alive. Sysprofd only needs to spawn it and then hand off the FD to the client.
-- Christian
