From: "David S. Miller" <davem@davemloft.net>
To: prasanna@in.ibm.com
Cc: akpm@osdl.org, ak@suse.de, linux-kernel@vger.kernel.org,
ananth@in.ibm.com, anil.s.keshavamurthy@intel.com,
systemtap@sources.redhat.com
Subject: Re: [PATCH] [5/5] Switch Kprobes inline functions to __kprobes for sparc64
Date: Sun, 09 Apr 2006 23:10:34 -0700 (PDT) [thread overview]
Message-ID: <20060409.231034.116564710.davem@davemloft.net> (raw)
In-Reply-To: <20060410060128.GD23879@in.ibm.com>
From: Prasanna S Panchamukhi <prasanna@in.ibm.com>
Date: Mon, 10 Apr 2006 11:31:28 +0530
> Andrew Morton pointed out that compiler might not inline the functions
> marked for inline in kprobes. There by allowing the insertion of probes
> on these kprobes routines, which might cause recursion. This patch
> removes all such inline and adds them to kprobes section there by
> disallowing probes on all such routines. Some of the routines can
> even still be inlined, since these routines gets executed after
> the kprobes had done necessay setup for reentrancy.
>
> Signed-off-by: Prasanna S Panchamukhi <prasanna@in.ibm.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2006-04-10 6:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 5:57 [PATCH] [1/5] Switch Kprobes inline functions to __kprobes for i386 Prasanna S Panchamukhi
2006-04-10 5:58 ` [PATCH] [2/5] Switch Kprobes inline functions to __kprobes for x86_64 Prasanna S Panchamukhi
2006-04-10 5:59 ` [PATCH] [3/5] Switch Kprobes inline functions to __kprobes for ppc64 Prasanna S Panchamukhi
2006-04-10 6:00 ` [PATCH] [4/5] Switch Kprobes inline functions to __kprobes for ia64 Prasanna S Panchamukhi
2006-04-10 6:01 ` [PATCH] [5/5] Switch Kprobes inline functions to __kprobes for sparc64 Prasanna S Panchamukhi
2006-04-10 6:10 ` David S. Miller [this message]
2006-04-11 2:41 ` [PATCH] [2/5] Switch Kprobes inline functions to __kprobes for x86_64 Andi Kleen
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=20060409.231034.116564710.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanna@in.ibm.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