diff options
| -rw-r--r-- | sys/arch/amiga/amiga/vm_machdep.c | 21 | ||||
| -rw-r--r-- | sys/arch/amiga/include/cpu.h | 3 | ||||
| -rw-r--r-- | sys/arch/i386/i386/vm_machdep.c | 24 | ||||
| -rw-r--r-- | sys/arch/mac68k/mac68k/vm_machdep.c | 23 |
4 files changed, 4 insertions, 67 deletions
diff --git a/sys/arch/amiga/amiga/vm_machdep.c b/sys/arch/amiga/amiga/vm_machdep.c index b1e15b10fe9..007291f885c 100644 --- a/sys/arch/amiga/amiga/vm_machdep.c +++ b/sys/arch/amiga/amiga/vm_machdep.c @@ -1,4 +1,4 @@ -/* $OpenBSD: vm_machdep.c,v 1.27 2001/11/30 22:38:22 miod Exp $ */ +/* $OpenBSD: vm_machdep.c,v 1.28 2001/12/07 00:59:13 miod Exp $ */ /* $NetBSD: vm_machdep.c,v 1.30 1997/05/19 10:14:50 veego Exp $ */ /* @@ -285,25 +285,6 @@ cpu_coredump(p, vp, cred, chdr) } /* - * Set a red zone in the kernel stack after the u. area. - * We don't support a redzone right now. It really isn't clear - * that it is a good idea since, if the kernel stack were to roll - * into a write protected page, the processor would lock up (since - * it cannot create an exception frame) and we would get no useful - * post-mortem info. Currently, under the DEBUG option, we just - * check at every clock interrupt to see if the current k-stack has - * gone too far (i.e. into the "redzone" page) and if so, panic. - * Look at _lev6intr in locore.s for more details. - */ -/*ARGSUSED*/ -void -setredzone(pte, vaddr) - u_int *pte; - caddr_t vaddr; -{ -} - -/* * Convert kernel VA to physical address */ int diff --git a/sys/arch/amiga/include/cpu.h b/sys/arch/amiga/include/cpu.h index ad4422a41f4..1e711202f62 100644 --- a/sys/arch/amiga/include/cpu.h +++ b/sys/arch/amiga/include/cpu.h @@ -1,4 +1,4 @@ -/* $OpenBSD: cpu.h,v 1.15 2001/11/30 23:20:09 miod Exp $ */ +/* $OpenBSD: cpu.h,v 1.16 2001/12/07 00:59:16 miod Exp $ */ /* $NetBSD: cpu.h,v 1.36 1996/09/11 00:11:42 thorpej Exp $ */ /* @@ -233,7 +233,6 @@ int dma_cachectl __P((caddr_t, int)); int kvtop __P((caddr_t)); void physaccess __P((caddr_t, caddr_t, int, int)); void physunaccess __P((caddr_t, int)); -void setredzone __P((u_int *, caddr_t)); #ifdef GENERIC /* diff --git a/sys/arch/i386/i386/vm_machdep.c b/sys/arch/i386/i386/vm_machdep.c index 7de82391532..d1c9dc219dc 100644 --- a/sys/arch/i386/i386/vm_machdep.c +++ b/sys/arch/i386/i386/vm_machdep.c @@ -1,4 +1,4 @@ -/* $OpenBSD: vm_machdep.c,v 1.33 2001/11/27 05:27:11 art Exp $ */ +/* $OpenBSD: vm_machdep.c,v 1.34 2001/12/07 00:59:16 miod Exp $ */ /* $NetBSD: vm_machdep.c,v 1.61 1996/05/03 19:42:35 christos Exp $ */ /*- @@ -70,8 +70,6 @@ extern struct proc *npxproc; #endif -void setredzone __P((u_short *, caddr_t)); - /* * Finish a fork operation, with process p2 nearly set up. * Copy and update the kernel stack and pcb, making the child @@ -246,26 +244,6 @@ cpu_coredump(p, vp, cred, chdr) return 0; } -#if 0 -/* - * Set a red zone in the kernel stack after the u. area. - */ -void -setredzone(pte, vaddr) - u_short *pte; - caddr_t vaddr; -{ -/* eventually do this by setting up an expand-down stack segment - for ss0: selector, allowing stack access down to top of u. - this means though that protection violations need to be handled - thru a double fault exception that must do an integral task - switch to a known good context, within which a dump can be - taken. a sensible scheme might be to save the initial context - used by sched (that has physical memory mapped 1:1 at bottom) - and take the dump while still in mapped mode */ -} -#endif - /* * Move pages from one kernel virtual address to another. * Both addresses are assumed to reside in the Sysmap. diff --git a/sys/arch/mac68k/mac68k/vm_machdep.c b/sys/arch/mac68k/mac68k/vm_machdep.c index 5981c3d3f9d..62b397d6d2c 100644 --- a/sys/arch/mac68k/mac68k/vm_machdep.c +++ b/sys/arch/mac68k/mac68k/vm_machdep.c @@ -1,4 +1,4 @@ -/* $OpenBSD: vm_machdep.c,v 1.26 2001/11/06 19:53:15 miod Exp $ */ +/* $OpenBSD: vm_machdep.c,v 1.27 2001/12/07 00:59:16 miod Exp $ */ /* $NetBSD: vm_machdep.c,v 1.29 1998/07/28 18:34:55 thorpej Exp $ */ /* @@ -283,27 +283,6 @@ physunaccess(vaddr, size) TBIAS(); } -void setredzone __P((void *, caddr_t)); - -/* - * Set a red zone in the kernel stack after the u. area. - * We don't support a redzone right now. It really isn't clear - * that it is a good idea since, if the kernel stack were to roll - * into a write protected page, the processor would lock up (since - * it cannot create an exception frame) and we would get no useful - * post-mortem info. Currently, under the DEBUG option, we just - * check at every clock interrupt to see if the current k-stack has - * gone too far (i.e. into the "redzone" page) and if so, panic. - * Look at _lev6intr in locore.s for more details. - */ -/*ARGSUSED*/ -void -setredzone(pte, vaddr) - void *pte; - caddr_t vaddr; -{ -} - int kvtop __P((caddr_t addr)); /* |