From: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
bhargavb <bhargavaramudu@gmail.com>,
linux-kernel@vger.kernel.org, Paul Clarke <pc@us.ibm.com>,
linux-rt-users@vger.kernel.org, linux-perf-users@vger.kernel.org,
Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/5] perf-probe: Improve probing on versioned symbols
Date: Thu, 7 Dec 2017 10:13:28 +0530 [thread overview]
Message-ID: <0db660f7-2211-39b0-7491-7fb3cc4fbb8f@linux.vnet.ibm.com> (raw)
In-Reply-To: <151252958056.12861.954203514347167563.stgit@devbox>
Hi Masami,
On 12/06/2017 08:36 AM, Masami Hiramatsu wrote:
> [4/5] Find versioned symbol from map without wildcard.
> This allows user to specify a symbol without version
> suffix nor wildcard. Anyway, at this point we have
> no way to specify version suffix, because parser
> recognizes "@" is a separator of "function@file"
> syntax. This is fixed in next patch.
> [5/5] Allow user to use backslash-escaped characters
> on command line. This has 2 effects, user can specify
> version suffix directly, and we can use special
> characters in source file.
Just a thought. Will it be good to describe / illustrate this
in man page as well?
Thanks,
Ravi
next prev parent reply other threads:[~2017-12-07 4:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 3:06 [PATCH 0/5] perf-probe: Improve probing on versioned symbols Masami Hiramatsu
2017-12-06 3:06 ` [PATCH 1/5] perf-probe: Add warning message if there is unexpected event name Masami Hiramatsu
2017-12-06 3:07 ` [PATCH 2/5] perf-probe: Cut off the version suffix from " Masami Hiramatsu
2017-12-06 3:07 ` [PATCH 3/5] perf-probe: Add __return suffix for return events Masami Hiramatsu
2017-12-06 3:08 ` [PATCH 4/5] perf-probe: Find versioned symbols from map Masami Hiramatsu
2017-12-06 3:08 ` [PATCH 5/5] perf-probe: Support escaped character in parser Masami Hiramatsu
2017-12-07 4:43 ` Ravi Bangoria [this message]
2017-12-07 6:11 ` [PATCH 0/5] perf-probe: Improve probing on versioned symbols Masami Hiramatsu
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=0db660f7-2211-39b0-7491-7fb3cc4fbb8f@linux.vnet.ibm.com \
--to=ravi.bangoria@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=bhargavaramudu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=pc@us.ibm.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;
as well as URLs for NNTP newsgroup(s).