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)
	Sun, Sep 6, 3:43 AM

	Unknown Object (File)
	Sat, Sep 5, 10:44 PM

	Unknown Object (File)
	Sat, Sep 5, 4:34 AM

	Unknown Object (File)
	Sat, Sep 5, 3:11 AM

	Unknown Object (File)
	Fri, Sep 4, 3:19 PM

	Unknown Object (File)
	Fri, Sep 4, 2:42 AM

	Unknown Object (File)
	Fri, Sep 4, 1:52 AM

	Unknown Object (File)
	Thu, Sep 3, 11:59 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.