summaryrefslogtreecommitdiff
path: root/src/lib/memset.c
diff options
context:
space:
mode:
authorAaron Durbin <adurbin@chromium.org>2013-05-06 12:20:52 -0500
committerRonald G. Minnich <rminnich@gmail.com>2013-05-14 05:18:47 +0200
commit4409a5eef6d1d669caad1bfe3fbefee87ea7734e (patch)
treea586c21f4def3f0ac3e318e2925facd85f23fff1 /src/lib/memset.c
parent8c8af592ca20e6c2dc48bea2c3ae66aa92c9dca7 (diff)
downloadcoreboot-4409a5eef6d1d669caad1bfe3fbefee87ea7734e.tar.xz
coreboot: add thread cooperative multitasking
The cooperative multitasking support allows the boot state machine to be ran cooperatively with other threads of work. The main thread still continues to run the boot state machine (src/lib/hardwaremain.c). All callbacks from the state machine are still ran synchronously from within the main thread's context. Without any other code added the only change to the boot sequence when cooperative multitasking is enabled is the queueing of an idlle thread. The idle thread is responsible for ensuring progress is made by calling timer callbacks. The main thread can yield to any other threads in the system. That means that anyone that spins up a thread must ensure no shared resources are used from 2 or more execution contexts. The support is originally intentioned to allow for long work itesm with busy loops to occur in parallel during a boot. Note that the intention on when to yield a thread will be on calls to udelay(). Change-Id: Ia4d67a38665b12ce2643474843a93babd8a40c77 Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: http://review.coreboot.org/3206 Tested-by: build bot (Jenkins) Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
Diffstat (limited to 'src/lib/memset.c')
0 files changed, 0 insertions, 0 deletions