From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 46751B7067 for ; Wed, 11 Nov 2009 10:20:49 +1100 (EST) Received: from az33smr02.freescale.net (az33smr02.freescale.net [10.64.34.200]) by az33egw02.freescale.net (8.14.3/az33egw02) with ESMTP id nAANKjSS018139 for ; Tue, 10 Nov 2009 16:20:45 -0700 (MST) Received: from az33exm25.fsl.freescale.net (az33exm25.am.freescale.net [10.64.32.16]) by az33smr02.freescale.net (8.13.1/8.13.0) with ESMTP id nAANKkCx020286 for ; Tue, 10 Nov 2009 17:20:46 -0600 (CST) Message-ID: <4AF9F56E.9080104@freescale.com> Date: Tue, 10 Nov 2009 17:21:18 -0600 From: Scott Wood MIME-Version: 1.0 To: Joakim Tjernlund Subject: Re: [PATCH 0/8] 8xx: Misc fixes for buggy insn References: <1257341920-29277-1-git-send-email-Joakim.Tjernlund@transmode.se> <20091106003305.GA15814@loki.buserror.net> <20091109215321.GA4351@loki.buserror.net> <20091109230004.GA24671@loki.buserror.net> <4AF99695.800@freescale.com> <4AF99B00.6080504@freescale.com> <4AF9CC99.1030500@freescale.com> <4AF9DCE0.4030805@freescale.com> <4AF9E2E2.7030100@freescale.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Cc: "linuxppc-dev@ozlabs.org" , Rex Feany List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Joakim Tjernlund wrote: > Scott Wood wrote on 10/11/2009 23:02:10: >> Joakim Tjernlund wrote: >> It wasn't the CPU15 workaround that I was worried about taking down the >> pinning -- but rather the CPU15 bug itself causing bad code to be >> executed inside the pinned kernel mapping. > > Oh, but then one is screwed anyway. Not if there's a workaround... >> However, the erratum says "MMU page", not "4K region", so I suppose if >> we have a pinned 8M page the problem could only occur at the end of the >> 8M (by which point the text segment should have ended). > > The wording makes me wonder why not a dcbi would fix the problem too. > Invalidate the problem cache lines and let the branch resolve. Where would you put the dcbi? How do you regain control after that cache line has been refilled, but before code flows back to the bad branch? -Scott