All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: don't infer VIPT I-cache properties from its reported geometry
Date: Fri, 30 Oct 2015 11:51:55 +0000	[thread overview]
Message-ID: <20151030115155.GF20030@arm.com> (raw)
In-Reply-To: <1446205603-14285-1-git-send-email-ard.biesheuvel@linaro.org>

On Fri, Oct 30, 2015 at 12:46:43PM +0100, Ard Biesheuvel wrote:
> The cache geometry reported by the CCSIDR system registers is tightly
> coupled to the instructions to perform cache maintenance by set/way,
> and the architecture explicitly forbids inferring anything about the
> actual cache geometry from them:
> 
>   The parameters NumSets, Associativity, and LineSize in these registers
>   define the architecturally visible parameters that are required for
>   the cache maintenance by Set/Way instructions. They are not guaranteed
>   to represent the actual microarchitectural features of a design. You
>   cannot make any inference about the actual sizes of caches based on
>   these parameters.
> 
> This includes calculating the way size of a VIPT I-cache to decide
> whether it is free of aliases. So remove the code that implements this
> for v7 CPUs, and treat all non-PIPT I-caches as aliasing instead.
> 
> Reported-by: Alex Van Brunt <avanbrunt@nvidia.com>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
>  arch/arm/kernel/setup.c | 11 +----------
>  1 file changed, 1 insertion(+), 10 deletions(-)
> 
> diff --git a/arch/arm/kernel/setup.c b/arch/arm/kernel/setup.c
> index 20edd349d379..1275135488ee 100644
> --- a/arch/arm/kernel/setup.c
> +++ b/arch/arm/kernel/setup.c
> @@ -279,7 +279,6 @@ int __pure cpu_architecture(void)
>  static int cpu_has_aliasing_icache(unsigned int arch)
>  {
>  	int aliasing_icache;
> -	unsigned int id_reg, num_sets, line_size;
>  
>  	/* PIPT caches never alias. */
>  	if (icache_is_pipt())
> @@ -288,15 +287,7 @@ static int cpu_has_aliasing_icache(unsigned int arch)
>  	/* arch specifies the register format */
>  	switch (arch) {
>  	case CPU_ARCH_ARMv7:
> -		asm("mcr	p15, 2, %0, c0, c0, 0 @ set CSSELR"
> -		    : /* No output operands */
> -		    : "r" (1));
> -		isb();
> -		asm("mrc	p15, 1, %0, c0, c0, 0 @ read CCSIDR"
> -		    : "=r" (id_reg));
> -		line_size = 4 << ((id_reg & 0x7) + 2);
> -		num_sets = ((id_reg >> 13) & 0x7fff) + 1;
> -		aliasing_icache = (line_size * num_sets) > PAGE_SIZE;
> +		aliasing_icache = 1;
>  		break;
>  	case CPU_ARCH_ARMv6:
>  		aliasing_icache = read_cpuid_cachetype() & (1 << 11);

I think this is the tip of the iceberg... If we have to audit/fix all
users of flush_pfn_alias and flush_icache_alias, we're in for some fun.

Will

      reply	other threads:[~2015-10-30 11:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30 11:46 [PATCH] ARM: don't infer VIPT I-cache properties from its reported geometry Ard Biesheuvel
2015-10-30 11:51 ` Will Deacon [this message]

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=20151030115155.GF20030@arm.com \
    --to=will.deacon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.