linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: Scott Wood <scottwood@freescale.com>,
	linuxppc-dev@ozlabs.org, Bob Cochran <ppc@mindchasers.com>,
	support@abatron.ch
Subject: Re: [RFC] [PATCH] powerpc: Add MSR_DE to MSR_KERNEL
Date: Sun, 03 Jun 2012 07:21:16 +1000	[thread overview]
Message-ID: <1338672076.7150.2.camel@pasglop> (raw)
In-Reply-To: <OFF2E739FE.A96EBAF2-ONC1257A11.00655546-C1257A11.0065978F@transmode.se>

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.

  reply	other threads:[~2012-06-02 21:21 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30  7:43 [RFC] [PATCH] powerpc: Add MSR_DE to MSR_KERNEL Joakim Tjernlund
2012-05-30  7:59 ` Dan Malek
2012-05-30 12:08   ` Re[2]: " Abatron Support
2012-05-31  9:05     ` Joakim Tjernlund
2012-05-31  9:30       ` Re[4]: " Abatron Support
2012-05-31  9:56         ` Joakim Tjernlund
2012-05-31 17:47           ` Scott Wood
2012-05-31 21:38             ` Joakim Tjernlund
2012-05-31 21:43               ` Scott Wood
2012-05-31 22:14                 ` Joakim Tjernlund
2012-05-31 22:16                   ` Scott Wood
2012-05-31 22:33                     ` Joakim Tjernlund
2012-05-31 22:35                     ` Joakim Tjernlund
2012-07-20  8:27                       ` Zang Roy-R61911
2012-07-20  8:37                         ` Joakim Tjernlund
2013-06-25  0:51                           ` Scott Wood
2013-06-25  6:00                             ` Joakim Tjernlund
2013-06-26 21:42                               ` Scott Wood
2012-06-01  9:12       ` Re[2]: " Benjamin Herrenschmidt
2012-06-01 10:34         ` Joakim Tjernlund
2012-05-30 13:26 ` Bob Cochran
2012-06-01  9:14   ` Benjamin Herrenschmidt
2012-06-01 10:38     ` Joakim Tjernlund
2012-06-01 16:28     ` Scott Wood
2012-06-01 22:30       ` Benjamin Herrenschmidt
2012-06-01 22:42         ` Scott Wood
2012-06-01 23:24           ` Benjamin Herrenschmidt
2012-06-02 18:29             ` Joakim Tjernlund
2012-06-02 21:21               ` Benjamin Herrenschmidt [this message]
2012-06-03  9:20                 ` Joakim Tjernlund
2012-06-04  9:06                 ` Joakim Tjernlund
     [not found]                 ` <OF7810EBD9.B191A242-ONC1257A13.0031E9E3-C1257A13.00320D10@LocalDomain>
2012-07-11 14:24                   ` Joakim Tjernlund
2012-07-11 14:45                     ` Kumar Gala

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=1338672076.7150.2.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=joakim.tjernlund@transmode.se \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=ppc@mindchasers.com \
    --cc=scottwood@freescale.com \
    --cc=support@abatron.ch \
    /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;
as well as URLs for NNTP newsgroup(s).