From: Ananth N Mavinakayanahalli <amavin@redhat.com>
To: rusty.lynch@intel.com
Cc: akpm@osdl.org, systemtap@sources.redhat.com,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
Hien Nguyen <hien@us.ibm.com>,
Prasanna S Panchamukhi <prasanna@in.ibm.com>,
Andi Kleen <ak@suse.de>,
linuxppc64-dev@ozlabs.org
Subject: Re: [patch 5/5] [kprobes] Tweak to the function return probe design
Date: Mon, 13 Jun 2005 15:48:15 -0400 [thread overview]
Message-ID: <42ADE2FF.5020604@redhat.com> (raw)
In-Reply-To: <20050613190323.672988000@tuna.jf.intel.com>
rusty.lynch@intel.com wrote:
Hi Rusty,
Thanks for doing this. However...
> +
> + orig_ret_address = (unsigned long)ri->ret_addr;
> + recycle_rp_inst(ri);
> +
> + if (orig_ret_address != (unsigned long) &kretprobe_trampoline)
> + /*
> + * This is the real return address. Any other
> + * instances associated with this task are for
> + * other calls deeper on the call stack
> + */
> + break;
> + }
> +
> + BUG_ON(!orig_ret_address);
> + regs->nip = orig_ret_address;
> +
> + unlock_kprobes();
> + preempt_enable_no_resched();
^^^^^^^
We don't need this here - on ppc64, we do a preempt_disable/enable in
kprobe_exceptions_notify() and so this will cause a spurious
preempt_enable().
Thanks,
Ananth
next parent reply other threads:[~2005-06-13 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050613190207.954385000@tuna.jf.intel.com>
[not found] ` <20050613190323.672988000@tuna.jf.intel.com>
2005-06-13 19:48 ` Ananth N Mavinakayanahalli [this message]
2005-06-13 20:51 [patch 0/5] [kprobes] Tweak to the function return probe design rusty.lynch
2005-06-13 20:51 ` [patch 5/5] " rusty.lynch
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=42ADE2FF.5020604@redhat.com \
--to=amavin@redhat.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=hien@us.ibm.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=prasanna@in.ibm.com \
--cc=rusty.lynch@intel.com \
--cc=systemtap@sources.redhat.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