ULE: provide defaults to ts_cpu
ClosedPublic
Actions

Authored by wma on Jan 16 2018, 7:53 AM.

Tags

None

Referenced Files

	Unknown Object (File)
	Sun, Nov 16, 12:59 AM

	Unknown Object (File)
	Sat, Nov 15, 1:41 PM

	Unknown Object (File)
	Wed, Nov 12, 12:36 AM

	Unknown Object (File)
	Tue, Nov 11, 7:39 AM

	Unknown Object (File)
	Mon, Nov 10, 11:50 AM

	Unknown Object (File)
	Mon, Nov 10, 6:23 AM

	Unknown Object (File)
	Mon, Nov 3, 5:56 PM

	Unknown Object (File)
	Mon, Nov 3, 5:56 PM

View All 60 Files

Subscribers

• hselasky

Details

Reviewers

jeff
nwhitehorn
imp
mw

Commits

rS328320: ULE: provide defaults to ts_cpu

Summary

Fix a bug when the system has no CPU 0. When created, threads were implicitly assigned to CPU 0. This had no practical effect since a real CPU was chosen immediately by the scheduler. However, on systems without a CPU 0, sched_ule attempted to access the scheduler queue of the "old" CPU when assigned the initial choice of the old one. This caused an attempt to use illegal memory and a crash (or, more usually, a deadlock). Fix this by assigned new threads to the BSP explicitly and add some asserts to see that this problem does not recur.