diff options
author | Joe Lawrence <joe.lawrence@redhat.com> | 2020-02-24 16:18:48 -0500 |
---|---|---|
committer | Michael Ellerman <mpe@ellerman.id.au> | 2020-03-13 21:13:06 +1100 |
commit | ffd3eaf178b0f616a071e510e289d937330b0b35 (patch) | |
tree | 1c975cfa9fab8b025d93c9e9825f38a6db820429 /drivers/cpufreq | |
parent | cc6f0e39000900e5dd1448103a9571f0eccd7d4e (diff) | |
download | linux-stable-ffd3eaf178b0f616a071e510e289d937330b0b35.tar.gz linux-stable-ffd3eaf178b0f616a071e510e289d937330b0b35.tar.bz2 linux-stable-ffd3eaf178b0f616a071e510e289d937330b0b35.zip |
powerpc/vdso: remove deprecated VDS64_HAS_DESCRIPTORS references
The original 2005 patch that introduced the powerpc vdso, pre-git
("ppc64: Implement a vDSO and use it for signal trampoline") notes that:
... symbols exposed by the vDSO aren't "normal" function symbols, apps
can't be expected to link against them directly, the vDSO's are both
seen as if they were linked at 0 and the symbols just contain offsets
to the various functions. This is done on purpose to avoid a
relocation step (ppc64 functions normally have descriptors with abs
addresses in them). When glibc uses those functions, it's expected to
use it's own trampolines that know how to reach them.
Despite that explanation, there remains dead #ifdef
VDS64_HAS_DESCRIPTORS code-blocks that provide alternate function
definitions that setup function descriptors.
Since VDS64_HAS_DESCRIPTORS has been unused for all these years, we
might as well finally remove it from the codebase.
Signed-off-by: Joe Lawrence <joe.lawrence@redhat.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20200224211848.26087-1-joe.lawrence@redhat.com
Diffstat (limited to 'drivers/cpufreq')
0 files changed, 0 insertions, 0 deletions