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

	F166731537: D10651.diff
	Sat, Aug 15, 10:01 PM

	Unknown Object (File)
	Fri, Aug 14, 9:01 PM

	Unknown Object (File)
	Wed, Aug 12, 1:18 PM

	Unknown Object (File)
	Wed, Aug 12, 1:18 PM

	Unknown Object (File)
	Wed, Aug 5, 9:50 PM

	Unknown Object (File)
	Mon, Aug 3, 9:13 PM

	Unknown Object (File)
	Fri, Jul 24, 2:30 PM

	Unknown Object (File)
	Tue, Jul 21, 12:34 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.