john stultz wrote: > Another issue with having a separate entry point for vgettimeofday is > that I don't quite understand how glibc detects if vsyscall is > available, and how deals with the vsyscall page moving around. Well, this is indeed a problem which needs an addition solution. If we'd look for the symbol, it's automatically handled. Likewise if the normal syscall handler does it magically. If a call to the magic address is needed we'd need from kind of version information in the vDSO to check for the existence of the extension. This check needs to be done for every call unless a new-enough kernel is assumed outright. One could add a functions to the vDSO which is called via the symbol table and which returns the necessary information to make the decision. The result would have to be stored in a local variable to avoid making that call over and over again. This all requires the PIC setup which makes the whole thing once again more expensive than the simple implicit table lookup. -- Ulrich Drepper Red Hat, Inc. 444 Castro St Mountain View, CA - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
References:
- [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchjohn stultz
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchUlrich Drepper
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchJamie Lokier
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchUlrich Drepper
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchJamie Lokier
- Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patchjohn stultz
- Prev by Date: Re: 2.6.2-rc2-bk1 oopses on boot (ACPI patch)
- Next by Date: Re: Patch: IPv6/AMD64: bug in net/ipv6/ndisc.c
- Previous by thread: Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patch
- Next by thread: Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patch
- Indexes:[Main][Thread]