From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Bob Cochran <ppc@mindchasers.com>,
support@abatron.ch
Subject: Re: [RFC] [PATCH] powerpc: Add MSR_DE to MSR_KERNEL
Date: Sat, 02 Jun 2012 09:24:59 +1000 [thread overview]
Message-ID: <1338593099.16119.60.camel@pasglop> (raw)
In-Reply-To: <4FC9456B.8090400@freescale.com>
On Fri, 2012-06-01 at 17:42 -0500, Scott Wood wrote:
> On 06/01/2012 05:30 PM, Benjamin Herrenschmidt wrote:
> > BTW. My point of view is that this whole business about MSR:DE is a HW
> > design bug. There should be -no- (absolutely 0) interaction between the
> > SW state and the HW debugger for normal operations unless the user of
> > the debugger explicitly wants to change some state.
>
> I agree entirely, and e500mc at least has less of this than e500v2 (not
> sure if it still needs MSR[DE], but supposedly it doesn't have the
> requirement for there to be a valid instruction at the debug vector,
> which is lots of fun when booting). But this isn't exactly something
> Freescale is going to replace existing chips over.
>
> Getting all the way to zero interaction would require a completely
> separate debug facility so software can debug at the same time. I'd be
> all for that (and let's throw in a third, for the hypervisor), but I'm
> not the one that needs to be convinced.
You can find a good compromise. If you have some kind of SPR letting you
know now many DACs and IACs are available, you could essentially
"reserve" some for HW debug with the probe. Not as good as a fully
separate facility but still better than stepping on each other toes.
Things like DBCR should probably still be separated. There's no excuse
for the MSR:DE bullshit tho :-)
Cheers,
Ben.
next prev parent reply other threads:[~2012-06-01 23:25 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 [this message]
2012-06-02 18:29 ` Joakim Tjernlund
2012-06-02 21:21 ` Benjamin Herrenschmidt
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=1338593099.16119.60.camel@pasglop \
--to=benh@kernel.crashing.org \
--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).