mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
Cc: hpa@zytor.com, mingo@redhat.com, tglx@linutronix.de,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Quark: Flush TLB via CR3 not CR4.PGE in setup_arch()
Date: Thu, 25 Sep 2014 06:57:55 +0200	[thread overview]
Message-ID: <20140925045755.GA20431@gmail.com> (raw)
In-Reply-To: <1411578452-4609-1-git-send-email-pure.logic@nexus-software.ie>


* Bryan O'Donoghue <pure.logic@nexus-software.ie> wrote:

> Quark X1000 requires CR3 to be rewritten to flush TLB entries
> irrespective of the PGE bits in CR4 or PTE.PGE
> 
> This patch flushes the TLB in the required way for Quark in setup_arch()
> See Quark Core_DevMan_001.pdf section 6.4.11
> 
> Signed-off-by: Bryan O'Donoghue <pure.logic@nexus-software.ie>
> ---
>  arch/x86/kernel/setup.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
> index 41ead8d..1d2396a 100644
> --- a/arch/x86/kernel/setup.c
> +++ b/arch/x86/kernel/setup.c
> @@ -879,7 +879,10 @@ void __init setup_arch(char **cmdline_p)
>  			KERNEL_PGD_PTRS);
>  
>  	load_cr3(swapper_pg_dir);
> -	__flush_tlb_all();
> +	if (boot_cpu_data.x86 == 5 && boot_cpu_data.x86_model == 9)
> +		__flush_tlb();
> +	else
> +		__flush_tlb_all();

So why not make __flush_tlb_all() Quark-quirk-aware and be done 
with it, instead of having to validate every single 
__flush_tlb_all() user?

Quark breaks the x86 'flush all TLBs' semantics - the way to fix 
it is to restore those semantics, not to sprinkle the breakage 
all around the code ...

Thanks,

	Ingo

  reply	other threads:[~2014-09-25  4:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24 17:07 Bryan O'Donoghue
2014-09-25  4:57 ` Ingo Molnar [this message]
2014-09-25  9:35   ` Bryan O'Donoghue
2014-09-25 14:51     ` Ingo Molnar
2014-09-25 15:04       ` Bryan O'Donoghue
2014-09-25 15:11         ` Ingo Molnar
2014-09-25 16:49           ` Henrique de Moraes Holschuh
2014-09-25 18:28             ` Ingo Molnar
2014-09-25 18:50               ` Bryan O'Donoghue
2014-09-25 18:59                 ` Ingo Molnar

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=20140925045755.GA20431@gmail.com \
    --to=mingo@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pure.logic@nexus-software.ie \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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

Powered by JetHome