02fb845bbf
kern_yield(0) effectively causes the calling thread to be rescheduled immediately since it resets the thread's priority to the highest possible value. This can cause livelocks when the pattern "while (!trylock()) kern_yield(0);" is used since the thread holding the lock may linger on the runqueue for the CPU on which the looping thread is running. MFC after: 1 week |
||
---|---|---|
.. | ||
ttm_agp_backend.c | ||
ttm_bo_api.h | ||
ttm_bo_driver.h | ||
ttm_bo_manager.c | ||
ttm_bo_util.c | ||
ttm_bo_vm.c | ||
ttm_bo.c | ||
ttm_execbuf_util.c | ||
ttm_execbuf_util.h | ||
ttm_lock.c | ||
ttm_lock.h | ||
ttm_memory.c | ||
ttm_memory.h | ||
ttm_module.h | ||
ttm_object.c | ||
ttm_object.h | ||
ttm_page_alloc_dma.c | ||
ttm_page_alloc.c | ||
ttm_page_alloc.h | ||
ttm_placement.h | ||
ttm_tt.c |