[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y73MBswL76Hi9cay@hirez.programming.kicks-ass.net>
Date: Tue, 10 Jan 2023 21:35:18 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Mark Rutland <mark.rutland@....com>
Cc: linux-arm-kernel@...ts.infradead.org, catalin.marinas@....com,
lenb@...nel.org, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org, mhiramat@...nel.org,
ndesaulniers@...gle.com, ojeda@...nel.org,
rafael.j.wysocki@...el.com, revest@...omium.org,
robert.moore@...el.com, rostedt@...dmis.org, will@...nel.org
Subject: Re: [PATCH 3/8] arm64: Extend support for CONFIG_FUNCTION_ALIGNMENT
On Mon, Jan 09, 2023 at 01:58:23PM +0000, Mark Rutland wrote:
> diff --git a/arch/arm64/include/asm/linkage.h b/arch/arm64/include/asm/linkage.h
> index 1436fa1cde24d..df18a3446ce82 100644
> --- a/arch/arm64/include/asm/linkage.h
> +++ b/arch/arm64/include/asm/linkage.h
> @@ -5,8 +5,14 @@
> #include <asm/assembler.h>
> #endif
>
> -#define __ALIGN .align 2
> -#define __ALIGN_STR ".align 2"
> +#if CONFIG_FUNCTION_ALIGNMENT > 0
> +#define ARM64_FUNCTION_ALIGNMENT CONFIG_FUNCTION_ALIGNMENT
> +#else
> +#define ARM64_FUNCTION_ALIGNMENT 4
> +#endif
> +
> +#define __ALIGN .balign ARM64_FUNCTION_ALIGNMENT
> +#define __ALIGN_STR ".balign " #ARM64_FUNCTION_ALIGNMENT
Isn't that much the same as having ARM64 select FUNCTION_ALIGNMENT_4B
and simply removing all these lines and relying on the default
behaviour?
Powered by blists - more mailing lists