linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Paul Burton <paul.burton@mips.com>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Cc: Paul Burton <pburton@wavecomp.com>
Subject: Re: [PATCH 3/3] MIPS: tlbex: Remove cpu_has_local_ebase
Date: Mon, 2 Sep 2019 01:19:29 +0200	[thread overview]
Message-ID: <9a58e8d4-73cf-9d18-8f67-04df5ad9ae91@amsat.org> (raw)
In-Reply-To: <20190831154027.6943-3-paul.burton@mips.com>

On 8/31/19 5:40 PM, Paul Burton wrote:
> The cpu_has_local_ebase macro is, confusingly, not used to indicate
> whether the EBase register is local to a CPU or not. Instead it
> indicates whether we want to generate the TLB refill exception vector
> each time a CPU is brought online. Doing this makes little sense on any
> system, since we always use the same value for EBase & thus we cannot
> have different TLB refill exception handlers per CPU.
> 
> Regenerating the code is not only pointless but also can be actively
> harmful, as commit 8759934e2b6b ("MIPS: Build uasm-generated code only
> once to avoid CPU Hotplug problem") described. That commit introduced
> cpu_has_local_ebase to disable the handler regeneration for Loongson
> machines, but this is by no means a Loongson-specific problem.
> 
> Remove cpu_has_local_ebase & simply generate the TLB refill handler once
> during boot, just like the rest of the TLB exception handlers.
> 
> Signed-off-by: Paul Burton <paul.burton@mips.com>
> ---
> 
>  arch/mips/include/asm/cpu-features.h                     | 3 ---
>  arch/mips/include/asm/mach-dec/cpu-feature-overrides.h   | 1 -
>  .../include/asm/mach-loongson64/cpu-feature-overrides.h  | 1 -
>  arch/mips/mm/tlbex.c                                     | 9 ++-------
>  4 files changed, 2 insertions(+), 12 deletions(-)
> 
> diff --git a/arch/mips/include/asm/cpu-features.h b/arch/mips/include/asm/cpu-features.h
> index 4e2bea8875f5..983a6a7f43a1 100644
> --- a/arch/mips/include/asm/cpu-features.h
> +++ b/arch/mips/include/asm/cpu-features.h
> @@ -243,9 +243,6 @@
>  #ifndef cpu_has_pindexed_dcache
>  #define cpu_has_pindexed_dcache	(cpu_data[0].dcache.flags & MIPS_CACHE_PINDEX)
>  #endif
> -#ifndef cpu_has_local_ebase
> -#define cpu_has_local_ebase	1
> -#endif
>  
>  /*
>   * I-Cache snoops remote store.	 This only matters on SMP.  Some multiprocessors
> diff --git a/arch/mips/include/asm/mach-dec/cpu-feature-overrides.h b/arch/mips/include/asm/mach-dec/cpu-feature-overrides.h
> index 1c11310bc8ad..00beb69bfab9 100644
> --- a/arch/mips/include/asm/mach-dec/cpu-feature-overrides.h
> +++ b/arch/mips/include/asm/mach-dec/cpu-feature-overrides.h
> @@ -32,7 +32,6 @@
>  #define cpu_has_vtag_icache		0
>  #define cpu_has_ic_fills_f_dc		0
>  #define cpu_has_pindexed_dcache		0
> -#define cpu_has_local_ebase		0
>  #define cpu_icache_snoops_remote_store	1
>  #define cpu_has_mips_4			0
>  #define cpu_has_mips_5			0
> diff --git a/arch/mips/include/asm/mach-loongson64/cpu-feature-overrides.h b/arch/mips/include/asm/mach-loongson64/cpu-feature-overrides.h
> index 581915ce231c..4aca25f2ff06 100644
> --- a/arch/mips/include/asm/mach-loongson64/cpu-feature-overrides.h
> +++ b/arch/mips/include/asm/mach-loongson64/cpu-feature-overrides.h
> @@ -43,7 +43,6 @@
>  #define cpu_has_vint		0
>  #define cpu_has_vtag_icache	0
>  #define cpu_has_watch		1
> -#define cpu_has_local_ebase	0
>  
>  #ifdef CONFIG_CPU_LOONGSON3
>  #define cpu_has_wsbh		1
> diff --git a/arch/mips/mm/tlbex.c b/arch/mips/mm/tlbex.c
> index 6e3ca9cc5249..e01cb33bfa1a 100644
> --- a/arch/mips/mm/tlbex.c
> +++ b/arch/mips/mm/tlbex.c
> @@ -2609,12 +2609,9 @@ void build_tlb_refill_handler(void)
>  
>  	if (cpu_has_3kex) {
>  #ifndef CONFIG_MIPS_PGD_C0_CONTEXT
> -		if (cpu_has_local_ebase)
> -			build_r3000_tlb_refill_handler();
>  		if (!run_once) {
> -			if (!cpu_has_local_ebase)
> -				build_r3000_tlb_refill_handler();
>  			build_setup_pgd();
> +			build_r3000_tlb_refill_handler();
>  			build_r3000_tlb_load_handler();
>  			build_r3000_tlb_store_handler();
>  			build_r3000_tlb_modify_handler();
> @@ -2638,13 +2635,11 @@ void build_tlb_refill_handler(void)
>  		build_r4000_tlb_modify_handler();
>  		if (cpu_has_ldpte)
>  			build_loongson3_tlb_refill_handler();
> -		else if (!cpu_has_local_ebase)
> +		else
>  			build_r4000_tlb_refill_handler();
>  		flush_tlb_handlers();
>  		run_once++;
>  	}
> -	if (cpu_has_local_ebase)
> -		build_r4000_tlb_refill_handler();
>  	if (cpu_has_xpa)
>  		config_xpa_params();
>  	if (cpu_has_htw)
> 

Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>

  reply	other threads:[~2019-09-01 23:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-31 15:40 [PATCH 1/3] MIPS: Select R3k-style TLB in Kconfig Paul Burton
2019-08-31 15:40 ` [PATCH 2/3] MIPS: tlbex: Simplify r3k check Paul Burton
2019-08-31 15:40 ` [PATCH 3/3] MIPS: tlbex: Remove cpu_has_local_ebase Paul Burton
2019-09-01 23:19   ` Philippe Mathieu-Daudé [this message]
2019-09-30  4:29   ` Maciej W. Rozycki
2019-09-01 22:54 ` [PATCH 1/3] MIPS: Select R3k-style TLB in Kconfig Philippe Mathieu-Daudé
2019-09-03 14:45 ` Paul Burton

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=9a58e8d4-73cf-9d18-8f67-04df5ad9ae91@amsat.org \
    --to=f4bug@amsat.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paul.burton@mips.com \
    --cc=pburton@wavecomp.com \
    /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;
as well as URLs for NNTP newsgroup(s).