From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev list <Linuxppc-dev@ozlabs.org>,
Torez Smith <torez@us.ibm.com>
Subject: Re: [RFC: PATCH 01/13] powerpc/booke: Add Stack Marking support to Booke Exception Prolog
Date: Tue, 02 Mar 2010 09:09:06 -0600 [thread overview]
Message-ID: <1267542546.32269.20.camel@norville.austin.ibm.com> (raw)
In-Reply-To: <68EF9A77-EB45-49D5-8496-686918DDC75C@kernel.crashing.org>
On Tue, 2010-03-02 at 08:50 -0600, Kumar Gala wrote:
> On Mar 1, 2010, at 1:13 PM, Dave Kleikamp wrote:
>
> > powerpc/booke: Add Stack Marking support to Booke Exception Prolog
> >
> > From: Torez Smith <lnxtorez@linux.vnet.ibm.com>
> >
> > Signed-off-by: Torez Smith <lnxtorez@linux.vnet.ibm.com>
> > Signed-off-by: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
> > ---
> >
> > arch/powerpc/kernel/head_booke.h | 5 +++++
> > 1 files changed, 5 insertions(+), 0 deletions(-)
>
> Can this be explained further as to what this gets us or does.
Yeah. Sorry about that. This is a debugging aid that identifies an
exception on the stack. xmon recognizes the marker and identifies the
exception frame in the stack trace. Other sub-architectures have it,
but bookE is currently missing it.
Ben, Torez,
Is there any reason this patch is re-defining STACK_FRAME_REGS_MARKER
rather than including asm/ptrace.h?
Thanks,
Shaggy
--
David Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2010-03-02 15:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 19:12 [RFC: PATCH 00/13] powerpc/47x: Support for 476 core Dave Kleikamp
2010-03-01 12:13 ` [RFC: PATCH 04/13] powerpc/476: add machine check handler for 47x core Dave Kleikamp
2010-03-01 21:08 ` Olof Johansson
2010-03-01 23:22 ` Dave Kleikamp
2010-03-01 19:13 ` [RFC: PATCH 01/13] powerpc/booke: Add Stack Marking support to Booke Exception Prolog Dave Kleikamp
2010-03-02 14:50 ` Kumar Gala
2010-03-02 15:09 ` Dave Kleikamp [this message]
2010-03-01 19:13 ` [RFC: PATCH 02/13] powerpc/44x: break out cpu init code into stand-alone function Dave Kleikamp
2010-03-01 19:13 ` [RFC: PATCH 03/13] powerpc/47x: Base ppc476 support Dave Kleikamp
2010-03-01 20:19 ` Josh Boyer
2010-03-01 23:11 ` Dave Kleikamp
2010-03-02 0:47 ` Josh Boyer
2010-03-01 19:13 ` [RFC: PATCH 05/13] powerpc/476: Add isync after loading mmu and debug spr's Dave Kleikamp
2010-03-01 19:13 ` [RFC: PATCH 07/13] powerpc/47x: defconfig for 476 on the iss 4xx simulator Dave Kleikamp
2010-03-01 19:13 ` [RFC: PATCH 08/13] powerpc/476: define specific cpu table entry for DD1 and DD1.1 cores Dave Kleikamp
2010-03-01 20:24 ` Josh Boyer
2010-03-01 23:43 ` Dave Kleikamp
2010-03-04 17:06 ` Hollis Blanchard
2010-03-05 9:15 ` Kumar Gala
2010-03-05 13:18 ` Dave Kleikamp
2010-03-01 19:13 ` [RFC: PATCH 09/13] powerpc/476: Workaround for dcbf/dcbz workaround on DD1 Dave Kleikamp
2010-03-01 19:14 ` [RFC: PATCH 10/13] powerpc/476: Add isync to the top of all exception handlers for DD1.1 core Dave Kleikamp
2010-03-01 19:14 ` [RFC: PATCH 11/13] powerpc/476: Software workaround to fix dcr read/write sequencing Dave Kleikamp
2010-03-01 19:14 ` [RFC: PATCH 12/13] powerpc/476: Workaround for DD1.1: Issue lwsync after mtpid Dave Kleikamp
2010-03-01 19:14 ` [RFC: PATCH 13/13] powerpc/476: Add dci instruction to async interrupt handlers on DD1 core Dave Kleikamp
2010-03-01 19:16 ` [RFC: PATCH 06/13] powerpc/4xx: Simple platform for the ISS 4xx simulator Dave Kleikamp
2010-03-01 20:29 ` Josh Boyer
2010-03-01 23:33 ` Dave Kleikamp
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=1267542546.32269.20.camel@norville.austin.ibm.com \
--to=shaggy@linux.vnet.ibm.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=galak@kernel.crashing.org \
--cc=torez@us.ibm.com \
/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).