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)
	Dec 20 2023, 3:08 AM

	Unknown Object (File)
	Nov 19 2023, 3:40 AM

	Unknown Object (File)
	Nov 7 2023, 9:41 PM

	Unknown Object (File)
	Nov 7 2023, 5:29 AM

	Unknown Object (File)
	Nov 5 2023, 2:31 PM

	Unknown Object (File)
	Oct 12 2023, 12:42 AM

	Unknown Object (File)
	Oct 6 2023, 8:34 PM

	Unknown Object (File)
	Oct 6 2023, 4:28 AM

View All 19 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.