On Thu, Apr 28, 2016 at 2:58 PM, Russell King
<rmk+kernel at arm.linux.org.uk> wrote:
> Provide a helper to indicate whether we need to perform special handling
> for boot identity mapping aliases or not.
>
> Signed-off-by: Russell King <rmk+kernel at arm.linux.org.uk>
> ---
> arch/arm/include/asm/memory.h | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/include/asm/memory.h b/arch/arm/include/asm/memory.h
> index ca208335fde6..31c07a2cc100 100644
> --- a/arch/arm/include/asm/memory.h
> +++ b/arch/arm/include/asm/memory.h
> @@ -295,6 +295,11 @@ extern long long arch_phys_to_idmap_offset;
> * of physical memory for idmap purposes. Most cases should leave these
> * untouched. Note: this can only return addresses less than 4GiB.
> */
> +static inline bool arm_has_idmap_alias(void)
> +{
> + return IS_ENABLED(CONFIG_MMU) && arch_phys_to_idmap_offset != 0;
> +}
> +
> #define IDMAP_INVALID_ADDR ((u32)~0)
>
> static inline unsigned long phys_to_idmap(phys_addr_t addr)
Reviewed-by: Pratyush Anand <panand at redhat.com>
