public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gioh Kim <gioh.kim@lge.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
	"David S. Miller" <davem@davemloft.net>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: How can I check creator of probe point?
Date: Thu, 16 Oct 2014 15:45:16 +0900	[thread overview]
Message-ID: <543F697C.6080808@lge.com> (raw)
In-Reply-To: <543F5EFA.7050209@hitachi.com>

I'm going to try them.
Thanks a lot.


2014-10-16 오후 3:00, Masami Hiramatsu 쓴 글:
> Hello Gioh,
> 
> If you can use ftrace and perftool, you can also put probes on
> caller site. perf-probe will give you source-code level probes.
> Or, just trace kmalloc event with ftrace stacktrace option, which
> gives you caller information so that you can filter your driver
> by postprocessing.
> 
> Thank you,
> 
> (2014/10/14 11:16), Gioh Kim wrote:
>>
>> Hi,
>>
>> I am trying to find a way to make statistics for memory allocation of my device driver.
>> I want to know how much memory it allocates and how many times it calls kmalloc().
>>
>> So I am considering to use kprobe but I think it doesn't provide a way to identify who makes the probe point.
>> Can I distinguish kmalloc() calling only from my driver?
>>
>> For example I think it could be like this:
>>
>> diff --git a/samples/kprobes/kretprobe_example.c b/samples/kprobes/kretprobe_example.c
>> index 1041b67..5322e0a 100644
>> --- a/samples/kprobes/kretprobe_example.c
>> +++ b/samples/kprobes/kretprobe_example.c
>> @@ -32,6 +32,7 @@ MODULE_PARM_DESC(func, "Function to kretprobe; this module will report the"
>>
>>   /* per-instance private data */
>>   struct my_data {
>> +       unsigned long signature;
>>          ktime_t entry_stamp;
>>   };
>>
>> @@ -43,8 +44,10 @@ static int entry_handler(struct kretprobe_instance *ri, struct pt_regs *regs)
>>          if (!current->mm)
>>                  return 1;       /* Skip kernel threads */
>>
>> -       data = (struct my_data *)ri->data;
>> -       data->entry_stamp = ktime_get();
>> +       if (signature == 0xabcdabcd) {
>> +               data = (struct my_data *)ri->data;
>> +               data->entry_stamp = ktime_get();
>> +       }
>>          return 0;
>>   }
>>
>> @@ -60,10 +63,12 @@ static int ret_handler(struct kretprobe_instance *ri, struct pt_regs *regs)
>>          s64 delta;
>>          ktime_t now;
>>
>> -       now = ktime_get();
>> -       delta = ktime_to_ns(ktime_sub(now, data->entry_stamp));
>> -       printk(KERN_INFO "%s returned %d and took %lld ns to execute\n",
>> -                       func_name, retval, (long long)delta);
>> +       if (signature == 0xabcdabcd) {
>> +               now = ktime_get();
>> +               delta = ktime_to_ns(ktime_sub(now, data->entry_stamp));
>> +               printk(KERN_INFO "%s returned %d and took %lld ns to execute\n",
>> +                      func_name, retval, (long long)delta);
>> +       }
>>          return 0;
>>   }
>>
>>
> 
> 

      reply	other threads:[~2014-10-16  6:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14  2:16 How can I check creator of probe point? Gioh Kim
2014-10-16  6:00 ` Masami Hiramatsu
2014-10-16  6:45   ` Gioh Kim [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=543F697C.6080808@lge.com \
    --to=gioh.kim@lge.com \
    --cc=ananth@in.ibm.com \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.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