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)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id A9389B6FA5 for ; Sun, 3 Jun 2012 07:21:36 +1000 (EST) Message-ID: <1338672076.7150.2.camel@pasglop> Subject: Re: [RFC] [PATCH] powerpc: Add MSR_DE to MSR_KERNEL From: Benjamin Herrenschmidt To: Joakim Tjernlund Date: Sun, 03 Jun 2012 07:21:16 +1000 In-Reply-To: References: <1338363814-19565-1-git-send-email-Joakim.Tjernlund@transmode.se> <4FC62018.3040404@mindchasers.com> <1338542089.16119.48.camel@pasglop> <4FC8EDC4.2050704@freescale.com> <1338589800.16119.58.camel@pasglop> <4FC9456B.8090400@freescale.com> <1338593099.16119.60.camel@pasglop> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Cc: Scott Wood , linuxppc-dev@ozlabs.org, Bob Cochran , support@abatron.ch List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sat, 2012-06-02 at 20:29 +0200, Joakim Tjernlund wrote: > > hmm, where does this go w.r.t the patch? Got the feeling that the > best thing is to just turn MSR:DE on and be done with it? Not unconditionally, we need to have a close look, that might be ok specifically for BookE 32-bit, it's certainly not ok for BookE 64-bit at this point. For now, I'm ok with a debug CONFIG_* option. Also do we know if MSR:DE has any performance impact on any CPU ? I know having DACs enabled has a major impact on some for example. Ben.