From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: peterz@infradead.org
Cc: mingo@redhat.com, alexander.shishkin@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: [PATCH V3 1/3] perf/core: Fixing filename for start/stop filters
Date: Thu, 11 Aug 2016 13:47:21 -0600 [thread overview]
Message-ID: <1470944843-7575-2-git-send-email-mathieu.poirier@linaro.org> (raw)
In-Reply-To: <1470944843-7575-1-git-send-email-mathieu.poirier@linaro.org>
Binary file names have to be supplied for both range and start/stop
filters but the current code only process the filename if an
address range filter is specified. This code adds processing of
the filename for start/stop filters.
Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
Acked-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
---
kernel/events/core.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index a19550d80ab1..0662279c5729 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -7905,8 +7905,10 @@ perf_event_parse_addr_filter(struct perf_event *event, char *fstr,
goto fail;
}
- if (token == IF_SRC_FILE) {
- filename = match_strdup(&args[2]);
+ if (token == IF_SRC_FILE || token == IF_SRC_FILEADDR) {
+ int fpos = filter->range ? 2 : 1;
+
+ filename = match_strdup(&args[fpos]);
if (!filename) {
ret = -ENOMEM;
goto fail;
--
2.7.4
next prev parent reply other threads:[~2016-08-11 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 19:47 [PATCH V3 0/3] perf/core: Miscellaneous fix for address filtering Mathieu Poirier
2016-08-11 19:47 ` Mathieu Poirier [this message]
2016-08-11 19:47 ` [PATCH V3 2/3] perf/core: Update filter only on executable mmap Mathieu Poirier
2016-08-11 19:47 ` [PATCH V3 3/3] perf/core: Enabling mapping of the stop filters Mathieu Poirier
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=1470944843-7575-2-git-send-email-mathieu.poirier@linaro.org \
--to=mathieu.poirier@linaro.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®