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)
	Thu, Oct 2, 11:38 PM

	Unknown Object (File)
	Thu, Oct 2, 2:22 PM

	Unknown Object (File)
	Thu, Oct 2, 2:33 AM

	Unknown Object (File)
	Wed, Oct 1, 9:15 PM

	Unknown Object (File)
	Wed, Oct 1, 2:03 PM

	Unknown Object (File)
	Mon, Sep 15, 6:03 AM

	Unknown Object (File)
	Sep 2 2025, 9:39 PM

	Unknown Object (File)
	Jul 28 2025, 11:09 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.