Searched hist:"8 ba3d077ff91f0713694522078eb6846fe18257b" (Results 1 – 5 of 5) sorted by relevance
| /freebsd/sys/powerpc/powerpc/ |
| H A D | vm_machdep.c | diff 8ba3d077ff91f0713694522078eb6846fe18257b Mon Jun 24 17:48:02 CEST 2002 Jake Burkholder <jake@FreeBSD.org> Add an MD callout like cpu_exit, but which is called after sched_lock is
obtained, when all other scheduling activity is suspended. This is needed
on sparc64 to deactivate the vmspace of the exiting process on all cpus.
Otherwise if another unrelated process gets the exact same vmspace structure
allocated to it (same address), its address space will not be activated
properly. This seems to fix some spontaneous signal 11 problems with smp
on sparc64.
diff 8ba3d077ff91f0713694522078eb6846fe18257b Mon Jun 24 17:48:02 CEST 2002 Jake Burkholder <jake@FreeBSD.org> Add an MD callout like cpu_exit, but which is called after sched_lock is
obtained, when all other scheduling activity is suspended. This is needed
on sparc64 to deactivate the vmspace of the exiting process on all cpus.
Otherwise if another unrelated process gets the exact same vmspace structure
allocated to it (same address), its address space will not be activated
properly. This seems to fix some spontaneous signal 11 problems with smp
on sparc64.
|
| /freebsd/sys/amd64/amd64/ |
| H A D | vm_machdep.c | diff 8ba3d077ff91f0713694522078eb6846fe18257b Mon Jun 24 17:48:02 CEST 2002 Jake Burkholder <jake@FreeBSD.org> Add an MD callout like cpu_exit, but which is called after sched_lock is
obtained, when all other scheduling activity is suspended. This is needed
on sparc64 to deactivate the vmspace of the exiting process on all cpus.
Otherwise if another unrelated process gets the exact same vmspace structure
allocated to it (same address), its address space will not be activated
properly. This seems to fix some spontaneous signal 11 problems with smp
on sparc64.
diff 8ba3d077ff91f0713694522078eb6846fe18257b Mon Jun 24 17:48:02 CEST 2002 Jake Burkholder <jake@FreeBSD.org> Add an MD callout like cpu_exit, but which is called after sched_lock is
obtained, when all other scheduling activity is suspended. This is needed
on sparc64 to deactivate the vmspace of the exiting process on all cpus.
Otherwise if another unrelated process gets the exact same vmspace structure
allocated to it (same address), its address space will not be activated
properly. This seems to fix some spontaneous signal 11 problems with smp
on sparc64.
|
| /freebsd/sys/i386/i386/ |
| H A D | vm_machdep.c | diff 8ba3d077ff91f0713694522078eb6846fe18257b Mon Jun 24 17:48:02 CEST 2002 Jake Burkholder <jake@FreeBSD.org> Add an MD callout like cpu_exit, but which is called after sched_lock is
obtained, when all other scheduling activity is suspended. This is needed
on sparc64 to deactivate the vmspace of the exiting process on all cpus.
Otherwise if another unrelated process gets the exact same vmspace structure
allocated to it (same address), its address space will not be activated
properly. This seems to fix some spontaneous signal 11 problems with smp
on sparc64.
diff 8ba3d077ff91f0713694522078eb6846fe18257b Mon Jun 24 17:48:02 CEST 2002 Jake Burkholder <jake@FreeBSD.org> Add an MD callout like cpu_exit, but which is called after sched_lock is
obtained, when all other scheduling activity is suspended. This is needed
on sparc64 to deactivate the vmspace of the exiting process on all cpus.
Otherwise if another unrelated process gets the exact same vmspace structure
allocated to it (same address), its address space will not be activated
properly. This seems to fix some spontaneous signal 11 problems with smp
on sparc64.
|
| /freebsd/sys/kern/ |
| H A D | kern_exit.c | diff 8ba3d077ff91f0713694522078eb6846fe18257b Mon Jun 24 17:48:02 CEST 2002 Jake Burkholder <jake@FreeBSD.org> Add an MD callout like cpu_exit, but which is called after sched_lock is
obtained, when all other scheduling activity is suspended. This is needed
on sparc64 to deactivate the vmspace of the exiting process on all cpus.
Otherwise if another unrelated process gets the exact same vmspace structure
allocated to it (same address), its address space will not be activated
properly. This seems to fix some spontaneous signal 11 problems with smp
on sparc64.
diff 8ba3d077ff91f0713694522078eb6846fe18257b Mon Jun 24 17:48:02 CEST 2002 Jake Burkholder <jake@FreeBSD.org> Add an MD callout like cpu_exit, but which is called after sched_lock is
obtained, when all other scheduling activity is suspended. This is needed
on sparc64 to deactivate the vmspace of the exiting process on all cpus.
Otherwise if another unrelated process gets the exact same vmspace structure
allocated to it (same address), its address space will not be activated
properly. This seems to fix some spontaneous signal 11 problems with smp
on sparc64.
|
| /freebsd/sys/sys/ |
| H A D | proc.h | diff 8ba3d077ff91f0713694522078eb6846fe18257b Mon Jun 24 17:48:02 CEST 2002 Jake Burkholder <jake@FreeBSD.org> Add an MD callout like cpu_exit, but which is called after sched_lock is
obtained, when all other scheduling activity is suspended. This is needed
on sparc64 to deactivate the vmspace of the exiting process on all cpus.
Otherwise if another unrelated process gets the exact same vmspace structure
allocated to it (same address), its address space will not be activated
properly. This seems to fix some spontaneous signal 11 problems with smp
on sparc64.
diff 8ba3d077ff91f0713694522078eb6846fe18257b Mon Jun 24 17:48:02 CEST 2002 Jake Burkholder <jake@FreeBSD.org> Add an MD callout like cpu_exit, but which is called after sched_lock is
obtained, when all other scheduling activity is suspended. This is needed
on sparc64 to deactivate the vmspace of the exiting process on all cpus.
Otherwise if another unrelated process gets the exact same vmspace structure
allocated to it (same address), its address space will not be activated
properly. This seems to fix some spontaneous signal 11 problems with smp
on sparc64.
|