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, Jan 10, 12:38 PM

	Unknown Object (File)
	Wed, Dec 25, 12:50 AM

	Unknown Object (File)
	Wed, Dec 25, 12:12 AM

	Unknown Object (File)
	Fri, Dec 20, 10:26 AM

	Unknown Object (File)
	Dec 5 2024, 1:40 AM

	Unknown Object (File)
	Nov 30 2024, 4:46 PM

	Unknown Object (File)
	Nov 30 2024, 12:02 PM

	Unknown Object (File)
	Nov 25 2024, 8:09 PM

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