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)
	Sat, Dec 27, 8:25 PM

	Unknown Object (File)
	Thu, Dec 25, 6:41 PM

	Unknown Object (File)
	Nov 21 2025, 12:43 AM

	Unknown Object (File)
	Nov 21 2025, 12:39 AM

	Unknown Object (File)
	Nov 21 2025, 12:38 AM

	Unknown Object (File)
	Nov 21 2025, 12:35 AM

	Unknown Object (File)
	Oct 26 2025, 4:27 PM

	Unknown Object (File)
	Oct 26 2025, 3:14 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.