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)
	Fri, Jul 24, 2:30 PM

	Unknown Object (File)
	Tue, Jul 21, 12:34 PM

	Unknown Object (File)
	Tue, Jul 21, 2:05 AM

	Unknown Object (File)
	Fri, Jul 10, 3:54 PM

	Unknown Object (File)
	Sun, Jun 28, 3:54 PM

	Unknown Object (File)
	Jun 25 2026, 12:51 AM

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

	Unknown Object (File)
	May 4 2026, 6:40 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.