• Mark Rutland's avatar
    arm64: Avoid cpus_have_const_cap() for ARM64_WORKAROUND_843419 · 0a285dfe
    Mark Rutland authored
    In count_plts() and is_forbidden_offset_for_adrp() we use
    cpus_have_const_cap() to check for ARM64_WORKAROUND_843419, but this is
    not necessary and cpus_have_final_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.
    
    It's not possible to load a module in the window between detecting the
    ARM64_WORKAROUND_843419 cpucap and patching alternatives. The module VA
    range limits are initialized much later in module_init_limits() which is
    a subsys_initcall, and module loading cannot happen before this. Hence
    it's not necessary for count_plts() or is_forbidden_offset_for_adrp() to
    use cpus_have_const_cap().
    
    This patch replaces the use of cpus_have_const_cap() with
    cpus_have_final_cap() which will avoid generating code to test the
    system_cpucaps bitmap and should be better for all subsequent calls at
    runtime. Using cpus_have_final_cap() clearly documents that we do not
    expect this code to run before cpucaps are finalized, and will make it
    easier to spot issues if code is changed in future to allow modules to
    be loaded earlier. The ARM64_WORKAROUND_843419 cpucap is added to
    cpucap_is_possible() so that code can be elided entirely when this is not
    possible, and redundant IS_ENABLED() checks are removed.
    Signed-off-by: default avatarMark Rutland <mark.rutland@arm.com>
    Cc: Ard Biesheuvel <ardb@kernel.org>
    Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
    Cc: Will Deacon <will@kernel.org>
    Signed-off-by: default avatarCatalin Marinas <catalin.marinas@arm.com>
    0a285dfe
module-plts.c 10.6 KB