From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Tiejun Chen <tiejun.chen@windriver.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [v3][PATCH 0/6] powerpc/book3e: make kgdb to work well
Date: Wed, 27 Feb 2013 11:09:01 +0800 [thread overview]
Message-ID: <512D78CD.7080903@windriver.com> (raw)
In-Reply-To: <1361934261-31840-1-git-send-email-tiejun.chen@windriver.com>
On 02/27/2013 11:04 AM, Tiejun Chen wrote:
> This patchset is used to support kgdb/gdb on book3e.
>
> Validated on p4080ds and p5040ds with test single step and breakpoint
Please ignore this thread since looks I'm missing to CC Jason :(
Tiejun
>
> v3:
>
> * make work when enable CONFIG_RELOCATABLE
> * fix one typo in patch,
> "powerpc/book3e: store critical/machine/debug exception thread info":
> ld r1,PACAKSAVE(r13);
> -> ld r14,PACAKSAVE(r13);
> * remove copying the thread_info since booke and book3e always copy
> the thead_info now when we enter the debug exception, and so drop
> the v2 patch, "book3e/kgdb: Fix a single stgep case of lazy IRQ"
>
> v2:
>
> * Make sure we cover CONFIG_PPC_BOOK3E_64 safely
> * Use LOAD_REG_IMMEDIATE() to load properly
> the value of the constant expression in load debug exception stack
> * Copy thread infor form the kernel stack coming from usr
> * Rebase latest powerpc git tree
>
> v1:
> * Copy thread info only when we are from !user mode since we'll get kernel stack
> coming from usr directly.
> * remove save/restore EX_R14/EX_R15 since DBG_EXCEPTION_PROLOG already covered
> this.
> * use CURRENT_THREAD_INFO() conveniently to get thread.
> * fix some typos
> * add a patch to make sure gdb can generate a single step properly to invoke a
> kgdb state.
> * add a patch to if we need to replay an interrupt, we shouldn't restore that
> previous backup thread info to make sure we can replay an interrupt lately
> with a proper thread info.
> * rebase latest powerpc git tree
>
> v0:
> This patchset is used to support kgdb for book3e.
>
> ------
> Tiejun Chen (6):
> powerpc/book3e: load critical/machine/debug exception stack
> powerpc/book3e: store critical/machine/debug exception thread info
> book3e/kgdb: update thread's dbcr0
> powerpc/book3e: support kgdb for kernel space
> kgdb/kgdbts: support ppc64
> powerpc/kgdb: remove copying the thread_info
>
> arch/powerpc/kernel/exceptions-64e.S | 69 ++++++++++++++++++++++++++++++++--
> arch/powerpc/kernel/kgdb.c | 41 +++++---------------
> drivers/misc/kgdbts.c | 2 +
> 3 files changed, 77 insertions(+), 35 deletions(-)
>
> Tiejun
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
>
next prev parent reply other threads:[~2013-02-27 3:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 3:04 [v3][PATCH 0/6] powerpc/book3e: make kgdb to work well Tiejun Chen
2013-02-27 3:04 ` [v3][PATCH 1/6] powerpc/book3e: load critical/machine/debug exception stack Tiejun Chen
2013-02-27 3:04 ` [v3][PATCH 2/6] powerpc/book3e: store critical/machine/debug exception thread info Tiejun Chen
2013-02-27 3:04 ` [v3][PATCH 3/6] book3e/kgdb: update thread's dbcr0 Tiejun Chen
2013-02-27 3:04 ` [v3][PATCH 4/6] powerpc/book3e: support kgdb for kernel space Tiejun Chen
2013-02-27 3:04 ` [v3][PATCH 5/6] kgdb/kgdbts: support ppc64 Tiejun Chen
2013-02-27 3:04 ` [v3][PATCH 6/6] powerpc/kgdb: remove copying the thread_info Tiejun Chen
2013-02-27 3:09 ` tiejun.chen [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-27 3:09 [v3][PATCH 0/6] powerpc/book3e: make kgdb to work well Tiejun Chen
2013-02-27 3:09 ` Tiejun Chen
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=512D78CD.7080903@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.