public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: update linker script to increased L1_CACHE_BYTES value
Date: Tue, 1 Dec 2015 12:40:47 +0000	[thread overview]
Message-ID: <20151201124046.GA6643@leverpostej> (raw)
In-Reply-To: <1448972440-32633-1-git-send-email-ard.biesheuvel@linaro.org>

On Tue, Dec 01, 2015 at 01:20:40PM +0100, Ard Biesheuvel wrote:
> Bring the linker script in line with the recent increase of
> L1_CACHE_BYTES to 128. Replace the hardcoded value of 64 with the
> symbolic constant.
> 
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>

I think we need to same substitution for RW_DATA_SECTION too, for
CACHELINE_ALIGNED_DATA(cacheline) and READ_MOSTLY_DATA(cacheline).

For 32-bit, Will made the same changes in f0d5375e3c7b5d7f ("ARM:
7289/1: vmlinux.lds.S: do not hardcode cacheline size as 32 bytes").

With that:

Acked-by: Mark Rutland <mark.rutland@arm.com>

Mark.

> ---
>  arch/arm64/kernel/vmlinux.lds.S | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm64/kernel/vmlinux.lds.S b/arch/arm64/kernel/vmlinux.lds.S
> index 1ee2c3937d4e..3388970fbc0f 100644
> --- a/arch/arm64/kernel/vmlinux.lds.S
> +++ b/arch/arm64/kernel/vmlinux.lds.S
> @@ -5,6 +5,7 @@
>   */
>  
>  #include <asm-generic/vmlinux.lds.h>
> +#include <asm/cache.h>
>  #include <asm/kernel-pgtable.h>
>  #include <asm/thread_info.h>
>  #include <asm/memory.h>
> @@ -140,7 +141,7 @@ SECTIONS
>  		ARM_EXIT_KEEP(EXIT_DATA)
>  	}
>  
> -	PERCPU_SECTION(64)
> +	PERCPU_SECTION(L1_CACHE_BYTES)
>  
>  	. = ALIGN(PAGE_SIZE);
>  	__init_end = .;
> -- 
> 1.9.1
> 

  reply	other threads:[~2015-12-01 12:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 12:20 [PATCH] arm64: update linker script to increased L1_CACHE_BYTES value Ard Biesheuvel
2015-12-01 12:40 ` Mark Rutland [this message]
2015-12-01 16:38   ` Catalin Marinas
2015-12-01 16:30 ` Catalin Marinas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151201124046.GA6643@leverpostej \
    --to=mark.rutland@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox