@rovarma@mastodon.gamedev.place
Post #2285611
2026-03-22 11:55 UTC
@michaelc@mastodon.gamedev.place Yep, that’s exactly what happens. It’s fine in this case because with the high sampling rate and the sporadic nature of the race, you’ll lose a few samples at most. And, the race is between the context switch and the sample, and we also collect stacks for cswitches, so the sample wouldn’t even give us any extra information since it would be the same stack (remember this is a same-CPU issue, so it effectively means you’d be sampling the cswitch).
Replies (1)
-
@rovarma@mastodon.gamedev.place 2026-03-22 11:55
@michaelc@mastodon.gamedev.place The sample interrupt is the only NMI we care about. There might be other NMIs on the system, but we don’t capture them.