Searched hist:170303 (Results 1 - 4 of 4) sorted by relevance
| /freebsd-10.2-release/sys/sparc64/sparc64/ | ||
| H A D | mp_machdep.c | diff 170303 Mon Jun 04 23:56:08 MDT 2007 jeff Commit 10/14 of sched_lock decomposition. - Use sched_throw() rather than replicating the same cpu_throw() code for each architecture. This also allows the scheduler to use any locking it may want to. - Use the thread_lock() rather than sched_lock when preempting. - The scheduler lock is not required to synchronize release_aps. Tested by: kris, current@ Tested on: i386, amd64, ULE, 4BSD, libthr, libkse, PREEMPTION, etc. Discussed with: kris, attilio, kmacy, jhb, julian, bde (small parts each) |
| /freebsd-10.2-release/sys/ia64/ia64/ | ||
| H A D | mp_machdep.c | diff 170303 Mon Jun 04 23:56:08 MDT 2007 jeff Commit 10/14 of sched_lock decomposition. - Use sched_throw() rather than replicating the same cpu_throw() code for each architecture. This also allows the scheduler to use any locking it may want to. - Use the thread_lock() rather than sched_lock when preempting. - The scheduler lock is not required to synchronize release_aps. Tested by: kris, current@ Tested on: i386, amd64, ULE, 4BSD, libthr, libkse, PREEMPTION, etc. Discussed with: kris, attilio, kmacy, jhb, julian, bde (small parts each) |
| /freebsd-10.2-release/sys/i386/i386/ | ||
| H A D | mp_machdep.c | diff 170303 Mon Jun 04 23:56:08 MDT 2007 jeff Commit 10/14 of sched_lock decomposition. - Use sched_throw() rather than replicating the same cpu_throw() code for each architecture. This also allows the scheduler to use any locking it may want to. - Use the thread_lock() rather than sched_lock when preempting. - The scheduler lock is not required to synchronize release_aps. Tested by: kris, current@ Tested on: i386, amd64, ULE, 4BSD, libthr, libkse, PREEMPTION, etc. Discussed with: kris, attilio, kmacy, jhb, julian, bde (small parts each) |
| /freebsd-10.2-release/sys/amd64/amd64/ | ||
| H A D | mp_machdep.c | diff 170303 Mon Jun 04 23:56:08 MDT 2007 jeff Commit 10/14 of sched_lock decomposition. - Use sched_throw() rather than replicating the same cpu_throw() code for each architecture. This also allows the scheduler to use any locking it may want to. - Use the thread_lock() rather than sched_lock when preempting. - The scheduler lock is not required to synchronize release_aps. Tested by: kris, current@ Tested on: i386, amd64, ULE, 4BSD, libthr, libkse, PREEMPTION, etc. Discussed with: kris, attilio, kmacy, jhb, julian, bde (small parts each) |
Completed in 160 milliseconds