[RFC PATCH v3 08/12] lib: vdso: allow arches to provide vdso data pointer

Thomas Gleixner tglx at linutronix.de
Tue Jan 14 15:06:01 PST 2020

Christophe Leroy <christophe.leroy at c-s.fr> writes:
>  static __maybe_unused int
> +__cvdso_clock_gettime_common(const struct vdso_data *vd, clockid_t clock,
> +		      struct __kernel_timespec *ts)
> +{
> +#else
>  __cvdso_clock_gettime_common(clockid_t clock, struct __kernel_timespec *ts)
>  {
>  	const struct vdso_data *vd = __arch_get_vdso_data();
> +#endif
>  	u32 msk;

If we do that, then there is no point in propagating this to the inner
functions. It's perfectly fine to have this distinction at the outermost

As a related question, I noticed that you keep all that ASM voodoo in
the PPC specific code which provides the actual entry points. Is that
ASM code really still necessary? All current users of the generic VDSO
just do something like:

int __vdso_clock_gettime(clockid_t clock, struct __kernel_timespec *ts)
        return __cvdso_clock_gettime(clock, ts);

in the architecture code. Is there a reason why this can't work on PPC?



More information about the linux-arm-kernel mailing list