All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Brendan Gregg <brendan.d.gregg@gmail.com>,
	"linux-perf-use." <linux-perf-users@vger.kernel.org>
Subject: Re: kprobe string
Date: Wed, 16 Jul 2014 22:41:02 -0600	[thread overview]
Message-ID: <53C753DE.6080306@gmail.com> (raw)
In-Reply-To: <CAE40pdfJpksb-LJghF+w4XZBagKo7wg6fh3irGPha5F9Uknb=A@mail.gmail.com>



On 07/16/2014 06:51 PM, Brendan Gregg wrote:
> G'Day,
>
> I'm not sure where else to ask this; I don't think this functionality
> is in perf_events yet...
>
> kprobes is supposed to be able to handle string arguments, but I've
> not been able to find a single working example. I'm trying (on 3.16):
>
> # cd /sys/kernel/debug/tracing
> # echo 'r:getname getname $retval:string' > kprobe_events
> -bash: echo: write error: Invalid argument
> # echo 'p:myprobe do_sys_open %dx:string' > kprobe_events
> -bash: echo: write error: Invalid argument
>
> I'm following the syntax in Documentation/trace/kprobetrace.txt by
> Masami Hiramatsu, and it is recognizing "string". But I'm getting
> these errors:
>
> # dmesg | tail -4
> [98021.813560] string type has no corresponding fetch method.
> [98021.813564] Parse error at argument[0]. (-22)
> [98705.956199] string type has no corresponding fetch method.
> [98705.956203] Parse error at argument[0]. (-22)
>
> Anyone seen this work? I'm checking the source... Thanks in advance,

Have you seen this:
https://lkml.org/lkml/2014/6/19/698

David

  reply	other threads:[~2014-07-17  4:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17  0:51 kprobe string Brendan Gregg
2014-07-17  4:41 ` David Ahern [this message]
2014-07-17  6:29   ` Brendan Gregg
2014-07-17  7:24     ` Namhyung Kim
2014-07-17  8:23       ` Brendan Gregg
2014-07-21  1:20         ` Brendan Gregg

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=53C753DE.6080306@gmail.com \
    --to=dsahern@gmail.com \
    --cc=brendan.d.gregg@gmail.com \
    --cc=linux-perf-users@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.