Nuke #if 0'ed "setredzone()" stub. We never used it, and probably

never will.  I've implemented an optional redzone as part of the KSE
upage breakup.

1 files changed, 0 insertions, 17 deletions

diff --git a/sys/ia64/ia64/vm_machdep.c b/sys/ia64/ia64/vm_machdep.c
index 59c1ac2..763a9e4 100644
--- a/sys/ia64/ia64/vm_machdep.c
+++ b/sys/ia64/ia64/vm_machdep.c
@@ -335,23 +335,6 @@ cpu_coredump(p, vp, cred)
 	    p));
 }
 
-#ifdef notyet
-static 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
-
 /*
  * Map an IO request into kernel virtual address space.
  *