All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: christophe leroy <christophe.leroy@c-s.fr>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Paul Mackerras <paulus@samba.org>,
	Scott Wood <scottwood@freescale.com>,
	Joakim Tjernlund <joakim.tjernlund@transmode.se>
Subject: Re: Time to get rid of CPU6 ERRATA on powerpc/8xx ?
Date: Sun, 7 Jan 2018 10:43:04 -0600	[thread overview]
Message-ID: <20180107164304.GA21977@gate.crashing.org> (raw)
In-Reply-To: <26b73379-141c-a705-a552-6ee2b94f4961@c-s.fr>

On Sun, Jan 07, 2018 at 05:23:13PM +0100, christophe leroy wrote:
> Today, Linux kernel includes a workaround for CPU6 ERRATA on the 8xx
> powerpc.
> 
> This ERRATA exists on the 801, the 823, the 855/860 before revision C.0
> It doesn't concern any modern versions of the 8xx, neither the 860 past
> and including rev C.0, nor the 866 nor the 885
> 
> This workaround complicates the TLBmiss and TLBerror handlers and make
> the code more and more unreadable.
> 
> Since this workaround addresses very old versions of the 8xx, I'd like
> to get rid of it. Do you see any good reason to keep it today ? If not I
> will come with a cleanup patch in the coming weeks.

What is "very old"?  It'll help if you give some indication.

Removing the workarounds is fine by me, of course...  Maybe make it fail
to boot though, with an error message?  Someone *will* try to run it on
an old system, *especially* if you think no one would.

Thanks,


Segher

  reply	other threads:[~2018-01-07 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-07 16:23 Time to get rid of CPU6 ERRATA on powerpc/8xx ? christophe leroy
2018-01-07 16:43 ` Segher Boessenkool [this message]
2018-01-07 17:51   ` christophe leroy
2018-01-07 18:21     ` Segher Boessenkool
2018-01-07 18:34 ` Joakim Tjernlund
2018-01-08  3:38 ` Michael Ellerman

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=20180107164304.GA21977@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=christophe.leroy@c-s.fr \
    --cc=joakim.tjernlund@transmode.se \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.org \
    --cc=scottwood@freescale.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 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.