From: "tiejun.chen" <tiejun.chen@windriver.com>
To: <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [v3 PATCH 0/3] ppc32/kprobe: Fix a bug for kprobe stwu r1
Date: Sun, 3 Jun 2012 13:14:21 +0800 [thread overview]
Message-ID: <4FCAF2AD.4040500@windriver.com> (raw)
In-Reply-To: <1338700063-30670-4-git-send-email-tiejun.chen@windriver.com>
On 06/03/2012 01:07 PM, Tiejun Chen wrote:
> Changes from V2:
>
> * populate those existed codes to reorganize codes
> * add check if we'll trigger kernel stack over flow
BTW, I always validate this on mpc8536ds(UP)/mpc8572ds(SMP) with/without
CONFIG_PREEMPT.
Tiejun
>
> Changes from V1:
>
> * use memcpy simply to withdraw copy_exc_stack
> * add !(regs->msr & MSR_PR)) and
> WARN_ON(test_thread_flag(TIF_EMULATE_STACK_STORE));
> to make sure we're in goot path.
> * move this migration process inside 'restore'
> * clear TIF flag atomically
>
> Tiejun Chen (3):
> powerpc/kprobe: introduce a new thread flag
> ppc32/kprobe: complete kprobe and migrate exception frame
> ppc32/kprobe: don't emulate store when kprobe stwu r1
>
> arch/powerpc/include/asm/thread_info.h | 3 ++
> arch/powerpc/kernel/entry_32.S | 43 ++++++++++++++++++++++++++-----
> arch/powerpc/lib/sstep.c | 37 ++++++++++++++++++++++++++-
> 3 files changed, 74 insertions(+), 9 deletions(-)
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
>
prev parent reply other threads:[~2012-06-03 5:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 5:07 [v3 PATCH 1/3] powerpc/kprobe: introduce a new thread flag Tiejun Chen
2012-06-03 5:07 ` [v3 PATCH 2/3] ppc32/kprobe: complete kprobe and migrate exception frame Tiejun Chen
2012-06-03 5:07 ` [v3 PATCH 3/3] ppc32/kprobe: don't emulate store when kprobe stwu r1 Tiejun Chen
2012-06-03 6:59 ` tiejun.chen
2012-06-03 7:10 ` tiejun.chen
2012-06-03 5:07 ` [v3 PATCH 0/3] ppc32/kprobe: Fix a bug for " Tiejun Chen
2012-06-03 5:14 ` tiejun.chen [this message]
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=4FCAF2AD.4040500@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@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 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).