From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Hansuk Hong <flavono123@gmail.com>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH] perf buildid-cache: Document for Node.js USDT
Date: Thu, 23 Nov 2017 14:48:15 -0300 [thread overview]
Message-ID: <20171123174815.GL8789@kernel.org> (raw)
In-Reply-To: <20171123160546.9722-1-flavono123@gmail.com>
Em Fri, Nov 24, 2017 at 01:05:46AM +0900, Hansuk Hong escreveu:
> Add a tip for Node.js USDT(User-Level Statically
> Defined Tracing) probes in tips.txt
Thanks, applid.
- Arnaldo
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Namhyung Kim <namhyung@kernel.org>
>
> Signed-off-by: Hansuk Hong <flavono123@gmail.com>
> ---
> tools/perf/Documentation/tips.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/perf/Documentation/tips.txt b/tools/perf/Documentation/tips.txt
> index db0ca3063eae..3dd1dbe28407 100644
> --- a/tools/perf/Documentation/tips.txt
> +++ b/tools/perf/Documentation/tips.txt
> @@ -32,3 +32,4 @@ Order by the overhead of source file name and line number: perf report -s srclin
> System-wide collection from all CPUs: perf record -a
> Show current config key-value pairs: perf config --list
> Show user configuration overrides: perf config --user --list
> +To add Node.js USDT(User-Level Statically Defined Tracing): perf buildid-cache --add `which node`
> --
> 2.14.2
next prev parent reply other threads:[~2017-11-23 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 16:05 [PATCH] perf buildid-cache: Document for Node.js USDT Hansuk Hong
2017-11-23 17:48 ` Arnaldo Carvalho de Melo [this message]
2017-12-06 16:33 ` [tip:perf/core] " tip-bot for Hansuk Hong
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=20171123174815.GL8789@kernel.org \
--to=acme@kernel.org \
--cc=flavono123@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@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.