lkml.org 
[lkml]   [2018]   [Jun]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH v3 03/20] arm64: Add a helper for PARange to physical shift conversion
    Date
    On arm64, ID_AA64MMFR0_EL1.PARange encodes the maximum Physical
    Address range supported by the CPU. Add a helper to decode this
    to actual physical shift. If we hit an unallocated value, return
    the maximum range supported by the kernel.
    This is will be used by the KVM to set the VTCR_EL2.T0SZ, as it
    is about to move its place. Having this helper keeps the code
    movement cleaner.

    Cc: Catalin Marinas <catalin.marinas@arm.com>
    Cc: Marc Zyngier <marc.zyngier@arm.com>
    Cc: James Morse <james.morse@arm.com>
    Cc: Christoffer Dall <cdall@kernel.org>
    Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
    ---
    Changes since V2:
    - Split the patch
    - Limit the physical shift only for values unrecognized.
    ---
    arch/arm64/include/asm/cpufeature.h | 13 +++++++++++++
    1 file changed, 13 insertions(+)

    diff --git a/arch/arm64/include/asm/cpufeature.h b/arch/arm64/include/asm/cpufeature.h
    index 1717ba1..855cf0e 100644
    --- a/arch/arm64/include/asm/cpufeature.h
    +++ b/arch/arm64/include/asm/cpufeature.h
    @@ -530,6 +530,19 @@ void arm64_set_ssbd_mitigation(bool state);
    static inline void arm64_set_ssbd_mitigation(bool state) {}
    #endif

    +static inline u32 id_aa64mmfr0_parange_to_phys_shift(int parange)
    +{
    + switch (parange) {
    + case 0: return 32;
    + case 1: return 36;
    + case 2: return 40;
    + case 3: return 42;
    + case 4: return 44;
    + case 5: return 48;
    + case 6: return 52;
    + default: return CONFIG_ARM64_PA_BITS;
    + }
    +}
    #endif /* __ASSEMBLY__ */

    #endif
    --
    2.7.4
    \
     
     \ /
      Last update: 2018-06-29 13:26    [W:5.220 / U:0.500 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site