Re: KPROBES: Instrumenting a function's call site

On 9/26/07, Ananth N Mavinakayanahalli <[email protected]> wrote:

> PS: There was a thought of providing a facility to run a handler at
> function entry even when just a kretprobe is used. Maybe we need to
> relook at that; it'd have been useful in this case.

That would be really useful. I was writing a tool to dump some
function profiling info through /proc. This would help save an extra
probe on each function's entry.

-
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • KPROBES: Instrumenting a function's call site
    • From: Avishay Traeger <[email protected]>
  • Re: KPROBES: Instrumenting a function's call site
    • From: Ananth N Mavinakayanahalli <[email protected]>

• Prev by Date: Re: [PATCH 10/25] Unionfs: add un/likely conditionals on copyup ops
• Next by Date: Re: sys_chroot+sys_fchdir Fix
• Previous by thread: Re: KPROBES: Instrumenting a function's call site
• Next by thread: Re: KPROBES: Instrumenting a function's call site
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]