Messages in this thread | | | Date | Thu, 26 Jul 2007 14:50:38 +0800 | From | "jidong xiao" <> | Subject | Re: What's does KPROBE_ENTRY mean? |
| |
Thanks.So if I don't care any probes, and I actually don't need to take use of kprobes, then I can use the functions defined through KPROBE_ENTRY() the same way as those defined via ENTRY(), right?
Regards Jason Xiao
On 7/26/07, Paul Mundt <lethal@linux-sh.org> wrote: > On Thu, Jul 26, 2007 at 01:43:10PM +0800, jidong xiao wrote: > > Anyone can help this? > > > > On 6/21/07, jidong xiao <jidong.xiao@gmail.com> wrote: > > > I searched in linux kernel 2.6.10, didn't find it, then I tried > > > 2.6.20, it is there. But I am not familiar with assembly language, so > > > can anybody kindly explain it, I don't know the difference between > > > KPROBE_ENTRY and ENTRY, however, I can find both of these items in > > > some files, such as arch/x86_64/kernel/entry.S. > > > > KPROBE_ENTRY() is the assembly equivalent of __kprobes, it places the > symbol in a special section (.kprobes.text) where probes can't be > inserted. This is usually helpful in cases where inserting the probe may > lead to recursion or other undesirable behaviour. > > See include/linux/linkage.h and include/linux/kprobes.h. > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |