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)
	Tue, Apr 7, 9:49 AM

	Unknown Object (File)
	Mon, Apr 6, 9:02 AM

	Unknown Object (File)
	Mon, Mar 30, 7:40 AM

	Unknown Object (File)
	Sat, Mar 21, 1:19 PM

	Unknown Object (File)
	Sat, Mar 21, 9:27 AM

	Unknown Object (File)
	Fri, Mar 20, 11:24 PM

	Unknown Object (File)
	Thu, Mar 12, 3:12 PM

	Unknown Object (File)
	Thu, Mar 12, 8:18 AM

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.