[lkml]   [2019]   [Sep]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] arm64: Allow disabling of the compat vDSO
On Wed, Sep 25, 2019 at 6:09 AM Catalin Marinas <> wrote:
> The compat vDSO building requires a cross-compiler than produces AArch32
> binaries, defined via CONFIG_CROSS_COMPILE_COMPAT_VDSO or the
> CROSS_COMPILE_COMPAT environment variable. If none of these is defined,
> building the kernel always prints a warning as there is no way to
> deselect the compat vDSO.
> Add an arm64 Kconfig entry to allow the deselection of the compat vDSO.
> In addition, make it an EXPERT option, default n, until other issues
> with the compat vDSO are solved (64-bit only kernel headers included in
> user-space vDSO code, CC_IS_CLANG irrelevant to CROSS_COMPILE_COMPAT).

CC_IS_CLANG might be because then CC can be reused with different
flags, rather than providing a different cross compiler binary via
config option.

> Fixes: bfe801ebe84f ("arm64: vdso: Enable vDSO compat support")
> Cc: Will Deacon <>
> Cc: Vincenzo Frascino <>
> Cc: Thomas Gleixner <>
> Signed-off-by: Catalin Marinas <>

Thanks for the patch.
Reviewed-by: Nick Desaulniers <>
Overall, this work is important to Android; the ARMv8-A series of
mobile SoCs we see today have to support 32b and 64b (A32+A64?) for at
least a few more years; we would like gettimeofday() and friends to be
fast for 32b and 64b applications.

> ---
> It looks like you can't really win with the current compat vDSO logic.
> You either don't have a compat cross-compiler and you get a Makefile
> warning or you have one and a get a compiler warning (or failure)
> because of the 64-bit kernel headers included in 32-bit user-space code.
> "depends on BROKEN" for ARM64_COMPAT_VDSO also work for me instead of
> EXPERT. I'll leave it up to Will to decide but I'd like at least this
> patch in -rc2 (even better if everything else is fixed before the final
> 5.4).
> Suggestions for future improvements of the compat vDSO handling:
> - replace the CROSS_COMPILE_COMPAT prefix with a full COMPATCC; maybe
> check that it indeed produces 32-bit code
> - check whether COMPATCC is clang or not rather than CC_IS_CLANG, which
> only checks the native compiler

When cross compiling, IIUC CC_IS_CLANG is referring to CC which is the
cross compiler, which is different than HOSTCC which is the host
compiler. HOSTCC is used mostly for things in scripts/ while CC is
used to compile a majority of the kernel in a cross compile.

> - clean up the headers includes; vDSO should not include kernel-only
> headers that may even contain code patched at run-time

This is a big one; Clang validates the inline asm constraints for
extended inline assembly, GCC does not for dead code. So Clang chokes
on the inclusion of arm64 headers using extended inline assembly when
being compiled for arm-linux-gnueabi.

> arch/arm64/Kconfig | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index 866e05882799..83a9a78085c6 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -110,7 +110,6 @@ config ARM64
> select HAVE_PCI
> @@ -1185,6 +1184,15 @@ config KUSER_HELPERS
> Say N here only if you are absolutely certain that you do not
> need these helpers; otherwise, the safe option is to say Y.
> +config ARM64_COMPAT_VDSO
> + bool "Enable the 32-bit vDSO" if EXPERT
> + depends on !CPU_BIG_ENDIAN
> + help
> + Enable the vDSO support for 32-bit applications. You would
> + need to set the 32-bit cross-compiler prefix in
> + environment variable.
> menuconfig ARMV8_DEPRECATED
> bool "Emulate deprecated/obsolete ARMv8 instructions"

~Nick Desaulniers

 \ /
  Last update: 2019-09-25 18:53    [W:0.077 / U:0.476 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site