1
0
mirror of https://github.com/0xAX/linux-insides.git synced 2024-12-22 06:38:07 +00:00

Merge pull request #729 from iAnatoly/master

clock_getres is added to vDSO for x86 as of Jun 22, 2019
This commit is contained in:
Sebastian Fricke 2020-09-12 09:48:38 +02:00 committed by GitHub
commit 738fefc3c3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -357,12 +357,13 @@ int arch_setup_additional_pages(struct linux_binprm *bprm, int uses_interp)
} }
``` ```
The `map_vdso` function is defined in the same source code file and maps pages for the `vDSO` and for the shared `vDSO` variables. That's all. The main differences between the `vsyscall` and the `vDSO` concepts is that `vsyscall` has a static address of `ffffffffff600000` and implements `3` system calls, whereas the `vDSO` loads dynamically and implements four system calls: The `map_vdso` function is defined in the same source code file and maps pages for the `vDSO` and for the shared `vDSO` variables. That's all. The main differences between the `vsyscall` and the `vDSO` concepts is that `vsyscall` has a static address of `ffffffffff600000` and implements three system calls, whereas the `vDSO` loads dynamically and implements five system calls, as defined in [arch/x86/entry/vdso/vma.c](https://github.com/torvalds/linux/blob/master/arch/x86/entry/vdso/vdso.lds.S):
* `__vdso_clock_gettime`; * `__vdso_clock_gettime`;
* `__vdso_getcpu`; * `__vdso_getcpu`;
* `__vdso_gettimeofday`; * `__vdso_gettimeofday`;
* `__vdso_time`. * `__vdso_time`;
* `__vdso_clock_getres`.
That's all. That's all.