mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Ingo Molnar <mingo@kernel.org>
Cc: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>,
	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 13:49:11 -0300	[thread overview]
Message-ID: <20140925164911.GD10814@khazad-dum.debian.net> (raw)
In-Reply-To: <20140925151123.GA4864@gmail.com>

On Thu, 25 Sep 2014, Ingo Molnar wrote:
> > If we're adding a comment though the first thing the comment ought to say is
> > what the code does for everybody else - stuff CR3 and flush the TLB, then it
> > should comment on the exception for Quark.
> > 
> > /*
> >  * Locate the page directory and flush the TLB.
> >  *
> >  * On Quark CPUs we still have the PGE bit set so
> >  * __flush_tlb_all() is not yet doing what it says - but
> >  * accidentally we have a cr3 flush here which is what is
> >  * needed - so there's no need to add a Quark quirk here.
> >  */
> > 
> > ?
> 
> Yeah, fair enough. You can even put the latter in parentheses, to 
> signal that it's all a rare case.

I'd have mentioned "erratum" there, otherwise people won't understand why
the PGE bit being set would be a problem in the first place.

Something like:

/*
 * Locate the page directory and flush the TLB.
 *
 * On Quark X1000 CPUs we still have the PGE bit incorrectly set
 * due to a processor erratum, so __flush_tlb_all() is not yet
 * doing what it says.  Fortunately we have a cr3 flush here,
 * which is what is needed in this processor to flush TLBs, so
 * there's no need to add a Quark X1000 quirk here.
 */

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2014-09-25 16:49 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
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 [this message]
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=20140925164911.GD10814@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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