From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3zF6F67268zF0RD for ; Mon, 8 Jan 2018 05:22:02 +1100 (AEDT) Date: Sun, 7 Jan 2018 12:21:42 -0600 From: Segher Boessenkool To: christophe leroy Cc: linuxppc-dev , Michael Ellerman , Paul Mackerras , Scott Wood , Joakim Tjernlund Subject: Re: Time to get rid of CPU6 ERRATA on powerpc/8xx ? Message-ID: <20180107182142.GC21977@gate.crashing.org> References: <26b73379-141c-a705-a552-6ee2b94f4961@c-s.fr> <20180107164304.GA21977@gate.crashing.org> <61f2b2bb-bdc0-39f5-81df-dc931494bb4b@c-s.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 In-Reply-To: <61f2b2bb-bdc0-39f5-81df-dc931494bb4b@c-s.fr> List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sun, Jan 07, 2018 at 06:51:26PM +0100, christophe leroy wrote: > Le 07/01/2018 à 17:43, Segher Boessenkool a écrit : > >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. > > CPU6 bug is already announced fixed in rev C.0 in revision 1.4 of the > ERRATA document, issued in August 2000. And that is the newest chip that had the bug? Wow, very old indeed then. > >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. > > Ok, will see how we can do that. It means identifying each revision of > the chip. If it is *that* old you may not have to bother... Up to the maintainers of course. Segher