• Mark Rutland's avatar
    arm64: Avoid cpus_have_const_cap() for ARM64_WORKAROUND_1742098 · 48b57d91
    Mark Rutland authored
    
    
    In elf_hwcap_fixup() we use cpus_have_const_cap() to check for
    ARM64_WORKAROUND_1742098, but this is not necessary and cpus_have_cap()
    would be preferable.
    
    For historical reasons, cpus_have_const_cap() is more complicated than
    it needs to be. Before cpucaps are finalized, it will perform a bitmap
    test of the system_cpucaps bitmap, and once cpucaps are finalized it
    will use an alternative branch. This used to be necessary to handle some
    race conditions in the window between cpucap detection and the
    subsequent patching of alternatives and static branches, where different
    branches could be out-of-sync with one another (or w.r.t. alternative
    sequences). Now that we use alternative branches instead of static
    branches, these are all patched atomically w.r.t. one another, and there
    are only a handful of cases that need special care in the window between
    cpucap detection and alternative patching.
    
    Due to the above, it would be nice to remove cpus_have_const_cap(), and
    migrate callers over to alternative_has_cap_*(), cpus_have_final_cap(),
    or cpus_have_cap() depending on when their requirements. This will
    remove redundant instructions and improve code generation, and will make
    it easier to determine how each callsite will behave before, during, and
    after alternative patching.
    
    The ARM64_WORKAROUND_1742098 cpucap is detected and patched before
    elf_hwcap_fixup() can run, and hence it is not necessary to use
    cpus_have_const_cap(). We run cpus_have_const_cap() at most twice: once
    after finalizing system cpucaps, and potentially once more after
    detecting mismatched CPUs which support AArch32 at EL0. Due to this,
    it's not necessary to optimize for many calls to elf_hwcap_fixup(), and
    it's fine to use cpus_have_cap().
    
    This patch replaces the use of cpus_have_const_cap() with
    cpus_have_cap(), which will only generate the bitmap test and avoid
    generating an alternative sequence, resulting in slightly simpler annd
    smaller code being generated. For consistenct with other cpucaps, the
    ARM64_WORKAROUND_1742098 cpucap is added to cpucap_is_possible() so that
    code can be elided when this is not possible. However, as we only define
    compat_elf_hwcap2 when CONFIG_COMPAT=y, some ifdeffery is still required
    within user_feature_fixup() to avoid build errors when CONFIG_COMPAT=n.
    Signed-off-by: default avatarMark Rutland <mark.rutland@arm.com>
    Cc: James Morse <james.morse@arm.com>
    Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
    Cc: Will Deacon <will@kernel.org>
    Signed-off-by: default avatarCatalin Marinas <catalin.marinas@arm.com>
    48b57d91
cpufeature.c 119 KB