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)
	Fri, Jun 7, 7:48 PM

	Unknown Object (File)
	Wed, May 22, 7:33 AM

	Unknown Object (File)
	Tue, May 21, 10:21 AM

	Unknown Object (File)
	Sat, May 18, 6:18 PM

	Unknown Object (File)
	May 1 2024, 7:28 AM

	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

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