Searched hist:"96 d7f8ef4663a90a8826c0b5ab56e9036dcb8506" (Results 1 – 5 of 5) sorted by relevance
/freebsd/sys/kern/ |
H A D | kern_time.c | diff 96d7f8ef4663a90a8826c0b5ab56e9036dcb8506 Mon Feb 17 11:03:02 CET 2003 Tim J. Robbins <tjr@FreeBSD.org> Use the proc lock to protect p_realtimer instead of Giant, and obtain sched_lock around accesses to p_stats->p_timer[] to avoid a potential race with hardclock. getitimer(), setitimer() and the realitexpire() callout are now Giant-free. diff 96d7f8ef4663a90a8826c0b5ab56e9036dcb8506 Mon Feb 17 11:03:02 CET 2003 Tim J. Robbins <tjr@FreeBSD.org> Use the proc lock to protect p_realtimer instead of Giant, and obtain sched_lock around accesses to p_stats->p_timer[] to avoid a potential race with hardclock. getitimer(), setitimer() and the realitexpire() callout are now Giant-free.
|
H A D | init_main.c | diff 96d7f8ef4663a90a8826c0b5ab56e9036dcb8506 Mon Feb 17 11:03:02 CET 2003 Tim J. Robbins <tjr@FreeBSD.org> Use the proc lock to protect p_realtimer instead of Giant, and obtain sched_lock around accesses to p_stats->p_timer[] to avoid a potential race with hardclock. getitimer(), setitimer() and the realitexpire() callout are now Giant-free. diff 96d7f8ef4663a90a8826c0b5ab56e9036dcb8506 Mon Feb 17 11:03:02 CET 2003 Tim J. Robbins <tjr@FreeBSD.org> Use the proc lock to protect p_realtimer instead of Giant, and obtain sched_lock around accesses to p_stats->p_timer[] to avoid a potential race with hardclock. getitimer(), setitimer() and the realitexpire() callout are now Giant-free.
|
H A D | kern_exit.c | diff 96d7f8ef4663a90a8826c0b5ab56e9036dcb8506 Mon Feb 17 11:03:02 CET 2003 Tim J. Robbins <tjr@FreeBSD.org> Use the proc lock to protect p_realtimer instead of Giant, and obtain sched_lock around accesses to p_stats->p_timer[] to avoid a potential race with hardclock. getitimer(), setitimer() and the realitexpire() callout are now Giant-free. diff 96d7f8ef4663a90a8826c0b5ab56e9036dcb8506 Mon Feb 17 11:03:02 CET 2003 Tim J. Robbins <tjr@FreeBSD.org> Use the proc lock to protect p_realtimer instead of Giant, and obtain sched_lock around accesses to p_stats->p_timer[] to avoid a potential race with hardclock. getitimer(), setitimer() and the realitexpire() callout are now Giant-free.
|
/freebsd/sys/compat/linux/ |
H A D | linux_misc.c | diff 96d7f8ef4663a90a8826c0b5ab56e9036dcb8506 Mon Feb 17 11:03:02 CET 2003 Tim J. Robbins <tjr@FreeBSD.org> Use the proc lock to protect p_realtimer instead of Giant, and obtain sched_lock around accesses to p_stats->p_timer[] to avoid a potential race with hardclock. getitimer(), setitimer() and the realitexpire() callout are now Giant-free. diff 96d7f8ef4663a90a8826c0b5ab56e9036dcb8506 Mon Feb 17 11:03:02 CET 2003 Tim J. Robbins <tjr@FreeBSD.org> Use the proc lock to protect p_realtimer instead of Giant, and obtain sched_lock around accesses to p_stats->p_timer[] to avoid a potential race with hardclock. getitimer(), setitimer() and the realitexpire() callout are now Giant-free.
|
/freebsd/sys/sys/ |
H A D | proc.h | diff 96d7f8ef4663a90a8826c0b5ab56e9036dcb8506 Mon Feb 17 11:03:02 CET 2003 Tim J. Robbins <tjr@FreeBSD.org> Use the proc lock to protect p_realtimer instead of Giant, and obtain sched_lock around accesses to p_stats->p_timer[] to avoid a potential race with hardclock. getitimer(), setitimer() and the realitexpire() callout are now Giant-free. diff 96d7f8ef4663a90a8826c0b5ab56e9036dcb8506 Mon Feb 17 11:03:02 CET 2003 Tim J. Robbins <tjr@FreeBSD.org> Use the proc lock to protect p_realtimer instead of Giant, and obtain sched_lock around accesses to p_stats->p_timer[] to avoid a potential race with hardclock. getitimer(), setitimer() and the realitexpire() callout are now Giant-free.
|