Fix profile/tick probe args when the probe fires from an idle thread
ClosedPublic
Actions

Authored by markj on May 8 2017, 10:56 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	May 11 2026, 10:58 AM

	Unknown Object (File)
	May 4 2026, 6:40 PM

	Unknown Object (File)
	May 3 2026, 5:47 PM

	Unknown Object (File)
	May 3 2026, 1:48 AM

	Unknown Object (File)
	Apr 28 2026, 11:54 PM

	Unknown Object (File)
	Apr 28 2026, 8:55 AM

	Unknown Object (File)
	Apr 25 2026, 8:51 PM

	Unknown Object (File)
	Apr 24 2026, 5:06 PM

View All Files

Subscribers

None

Details

Reviewers

avg

Commits

rS318319: Ensure that profile and tick probes provide a non-zero PC value.

Summary

If we don't have an interrupt frame and the running thread is an idle
thread, pass the address of cpu_idle() for arg0. This ensures that one
of the probe arguments is non-zero. At least one of the profile
provider tests expects this, and &cpu_idle seems like a reasonable
representative value for this case.