Searched hist:fc5243d98ac2575ad14a974b3c097e9ba874c03d (Results 1 – 6 of 6) sorted by relevance
| /linux/arch/sh/kernel/vsyscall/ |
| H A D | vsyscall.c | diff fc5243d98ac2575ad14a974b3c097e9ba874c03d Thu Dec 25 13:38:35 CET 2008 Martin Schwidefsky <schwidefsky@de.ibm.com> [S390] arch_setup_additional_pages arguments
arch_setup_additional_pages currently gets two arguments, the binary
format descripton and an indication if the process uses an executable
stack or not. The second argument is not used by anybody, it could
be removed without replacement.
What actually does make sense is to pass an indication if the process
uses the elf interpreter or not. The glibc code will not use anything
from the vdso if the process does not use the dynamic linker, so for
statically linked binaries the architecture backend can choose not
to map the vdso.
Acked-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
|
| /linux/arch/sh/include/asm/ |
| H A D | elf.h | diff fc5243d98ac2575ad14a974b3c097e9ba874c03d Thu Dec 25 13:38:35 CET 2008 Martin Schwidefsky <schwidefsky@de.ibm.com> [S390] arch_setup_additional_pages arguments
arch_setup_additional_pages currently gets two arguments, the binary
format descripton and an indication if the process uses an executable
stack or not. The second argument is not used by anybody, it could
be removed without replacement.
What actually does make sense is to pass an indication if the process
uses the elf interpreter or not. The glibc code will not use anything
from the vdso if the process does not use the dynamic linker, so for
statically linked binaries the architecture backend can choose not
to map the vdso.
Acked-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
|
| /linux/arch/powerpc/include/asm/ |
| H A D | elf.h | diff fc5243d98ac2575ad14a974b3c097e9ba874c03d Thu Dec 25 13:38:35 CET 2008 Martin Schwidefsky <schwidefsky@de.ibm.com> [S390] arch_setup_additional_pages arguments
arch_setup_additional_pages currently gets two arguments, the binary
format descripton and an indication if the process uses an executable
stack or not. The second argument is not used by anybody, it could
be removed without replacement.
What actually does make sense is to pass an indication if the process
uses the elf interpreter or not. The glibc code will not use anything
from the vdso if the process does not use the dynamic linker, so for
statically linked binaries the architecture backend can choose not
to map the vdso.
Acked-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
|
| /linux/arch/x86/include/asm/ |
| H A D | elf.h | diff fc5243d98ac2575ad14a974b3c097e9ba874c03d Thu Dec 25 13:38:35 CET 2008 Martin Schwidefsky <schwidefsky@de.ibm.com> [S390] arch_setup_additional_pages arguments
arch_setup_additional_pages currently gets two arguments, the binary
format descripton and an indication if the process uses an executable
stack or not. The second argument is not used by anybody, it could
be removed without replacement.
What actually does make sense is to pass an indication if the process
uses the elf interpreter or not. The glibc code will not use anything
from the vdso if the process does not use the dynamic linker, so for
statically linked binaries the architecture backend can choose not
to map the vdso.
Acked-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
|
| /linux/arch/powerpc/kernel/ |
| H A D | vdso.c | diff fc5243d98ac2575ad14a974b3c097e9ba874c03d Thu Dec 25 13:38:35 CET 2008 Martin Schwidefsky <schwidefsky@de.ibm.com> [S390] arch_setup_additional_pages arguments
arch_setup_additional_pages currently gets two arguments, the binary
format descripton and an indication if the process uses an executable
stack or not. The second argument is not used by anybody, it could
be removed without replacement.
What actually does make sense is to pass an indication if the process
uses the elf interpreter or not. The glibc code will not use anything
from the vdso if the process does not use the dynamic linker, so for
statically linked binaries the architecture backend can choose not
to map the vdso.
Acked-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
|
| /linux/fs/ |
| H A D | binfmt_elf.c | diff fc5243d98ac2575ad14a974b3c097e9ba874c03d Thu Dec 25 13:38:35 CET 2008 Martin Schwidefsky <schwidefsky@de.ibm.com> [S390] arch_setup_additional_pages arguments
arch_setup_additional_pages currently gets two arguments, the binary
format descripton and an indication if the process uses an executable
stack or not. The second argument is not used by anybody, it could
be removed without replacement.
What actually does make sense is to pass an indication if the process
uses the elf interpreter or not. The glibc code will not use anything
from the vdso if the process does not use the dynamic linker, so for
statically linked binaries the architecture backend can choose not
to map the vdso.
Acked-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
|