All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: He Kuang <hekuang@huawei.com>
Cc: jolsa@kernel.org, a.p.zijlstra@chello.nl, acme@kernel.org,
	mingo@redhat.com, wangnan0@huawei.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] tools lib traceevent: Export dynamic symbols used by traceevent plugins
Date: Sun, 24 May 2015 20:50:10 +0200	[thread overview]
Message-ID: <20150524185009.GA2969@krava.local> (raw)
In-Reply-To: <1431676879-19724-1-git-send-email-hekuang@huawei.com>

On Fri, May 15, 2015 at 08:01:18AM +0000, He Kuang wrote:

SNIP

>            :1049  1049 [000]  9666.754487: ftrace:function:  ffffffff8118bc50 <-- ffffffff8118c5b3
>            :1049  1049 [000]  9666.754487: ftrace:function:  ffffffff818e2440 <-- ffffffff8118bc75
>            :1049  1049 [000]  9666.754487: ftrace:function:  ffffffff8106eee0 <-- ffffffff811212e2
> 
> After this patch:
> 
>   $ perf record -e 'ftrace:function' ls
>   $ perf script
>            :1049  1049 [000]  9666.754487: ftrace:function: __set_task_comm
>            :1049  1049 [000]  9666.754487: ftrace:function:    _raw_spin_lock
>            :1049  1049 [000]  9666.754487: ftrace:function: task_tgid_nr_ns
>            ...
> 
> Signed-off-by: He Kuang <hekuang@huawei.com>

sorry for the delay..

Acked-by: Jiri Olsa <jolsa@kernel.org>

thanks,
jirka

      parent reply	other threads:[~2015-05-24 18:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15  8:01 [PATCH v3 1/2] tools lib traceevent: Export dynamic symbols used by traceevent plugins He Kuang
2015-05-15  8:01 ` [PATCH v3 2/2] tools lib traceevent: Ignore libtrace-dynamic-list file He Kuang
2015-05-24  8:30 ` [PATCH v3 1/2] tools lib traceevent: Export dynamic symbols used by traceevent plugins He Kuang
2015-05-24 18:50 ` Jiri Olsa [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=20150524185009.GA2969@krava.local \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=hekuang@huawei.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=wangnan0@huawei.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 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.