Kyle Evans 00bc7bbde5 sched: separate out schedinit_ap() ... schedinit_ap() sets up an AP for a later call to sched_throw(NULL). Currently, ULE sets up some pcpu bits and fixes the idlethread lock with a call to sched_throw(NULL); this results in a window where curthread is setup in platforms' init_secondary(), but it has the wrong td_lock. Typical platform AP startup procedure looks something like: - Setup curthread - ... other stuff, including cpu_initclocks_ap() - Signal smp_started - sched_throw(NULL) to enter the scheduler cpu_initclocks_ap() may have callouts to process (e.g., nvme) and attempt to sched_add() for this AP, but this attempt fails because of the noted violated assumption leading to locking heartburn in sched_setpreempt(). Interrupts are still disabled until cpu_throw() so we're not really at risk of being preempted -- just let the scheduler in on it a little earlier as part of setting up curthread. (cherry picked from commit 589aed00e3)		2022-02-10 14:55:29 -06:00
..
conf	riscv: gdb(4) support	2022-01-19 14:30:31 -04:00
include	Remove "All Rights Reserved" from FreeBSD Foundation sys/ copyrights	2022-02-08 15:00:55 -05:00
riscv	sched: separate out schedinit_ap()	2022-02-10 14:55:29 -06:00
sifive	sifive_spi: Add missing case for SPIBUS_MODE_NONE	2021-09-07 13:08:20 +01:00