Messages in this thread | | | Subject | Re: [patch] i386, vdso=[0|1] boot option and /proc/sys/vm/vdso_enabled | From | Rusty Russell <> | Date | Sun, 21 May 2006 14:38:17 +1000 |
| |
On Sat, 2006-05-20 at 03:04 -0700, Zachary Amsden wrote: > >> Index: linux-2.6.17-rc/include/asm-i386/fixmap.h > >> =================================================================== > >> --- linux-2.6.17-rc.orig/include/asm-i386/fixmap.h 2006-03-19 21:53:29.000000000 -0800 > >> +++ linux-2.6.17-rc/include/asm-i386/fixmap.h 2006-05-19 18:16:00.000000000 -0700 > >> @@ -20,7 +20,7 @@ > >> * Leave one empty page between vmalloc'ed areas and > >> * the start of the fixmap. > >> */ > >> -#define __FIXADDR_TOP 0xfffff000 > >> +#define __FIXADDR_TOP 0xffbff000 > >> > > > > The machine runs OK with that applied and with > > move-vsyscall-page-out-of-fixmap-into-normal-vma-as-per-mmap.patch not > > applied. > > > > Err. That implies that there is likely a problem in the kernel patch, > not in userspace, Let's look more closely at > move-vsyscall-page-out-of-fixmap-into-normal-vma-as-per-mmap and see if > there is something missing.
Indeed. And I really hate the idea of a global switch for this, too: it should just work, or autodetect (esp if it's init that failing, this might be possible).
Off to find FC1... Rusty. -- ccontrol: http://ccontrol.ozlabs.org
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |