Messages in this thread |  | | Date | Sun, 20 Oct 2002 04:56:09 +0200 | | From | Andi Kleen <> | | Subject | Re: [PATCH] linux-2.5.43_vsyscall_A0 |
| |
On Sun, Oct 20, 2002 at 03:50:37AM +0200, Rik van Riel wrote: > On Fri, 18 Oct 2002, Jeff Dike wrote: > > > My preferred solution would be for libc to ask the kernel where the > > vsyscall area is. That's reasonably clean and virtualizable. Andrea > > doesn't like it because it adds a few instructions to the vsyscall > > address calculation. > > Sounds like the best solution indeed, especially when keeping > in mind the strange people who want to run with a different > user:kernel split or statically linked binaries at fun addresses > so they've got more space for their fortran arrays ;)
x86-64 addresses that (not that it would need it) by putting vsyscalls at the top of the virtual mapping after the direct mapped area. This part never moves even with changed __PAGE_OFFSET. The same technique should work on i386 too.
-Andi - 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/
|  |