From: Andi Kleen <andi@firstfloor.org>
To: peterz@infradead.org
Cc: alexander.shishkin@linux.intel.com, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: [PATCH 1/2] perf/core: Allow global address filtering for kernel code
Date: Fri, 3 Feb 2017 14:18:29 -0800 [thread overview]
Message-ID: <20170203221830.22354-1-andi@firstfloor.org> (raw)
From: Andi Kleen <ak@linux.intel.com>
The address filter code disallows filtering for per-cpu events,
because it would require dynamically changing user address filters
in context switches.
For the special case of filtering on kernel code only,
we can allow it, as the kernel code always stays at the same
addresses.
So move the check for the global filter in the parser code
and only check after we know there are user space filters.
In addition also handle this case when applying the filter.
Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
kernel/events/core.c | 26 +++++++++++++++++---------
1 file changed, 17 insertions(+), 9 deletions(-)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index 110b38a58493..15fd58177e73 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -8016,6 +8016,9 @@ static void perf_event_addr_filters_apply(struct perf_event *event)
if (task == TASK_TOMBSTONE)
return;
+ if (!event->ctx->task)
+ goto restart;
+
mm = get_task_mm(event->ctx->task);
if (!mm)
goto restart;
@@ -8190,6 +8193,20 @@ perf_event_parse_addr_filter(struct perf_event *event, char *fstr,
goto fail;
if (!kernel) {
+ /*
+ * For now, we only support user
+ * filtering in per-task events; doing
+ * so for CPU-wide events requires
+ * additional context switching
+ * trickery, since same object code
+ * will be mapped at different virtual
+ * addresses in different processes.
+ */
+ ret = -EOPNOTSUPP;
+ if (!event->ctx->task)
+ goto fail;
+
+ ret = -EINVAL;
if (!filename)
goto fail;
@@ -8247,15 +8264,6 @@ perf_event_set_addr_filter(struct perf_event *event, char *filter_str)
if (WARN_ON_ONCE(event->parent))
return -EINVAL;
- /*
- * For now, we only support filtering in per-task events; doing so
- * for CPU-wide events requires additional context switching trickery,
- * since same object code will be mapped at different virtual
- * addresses in different processes.
- */
- if (!event->ctx->task)
- return -EOPNOTSUPP;
-
ret = perf_event_parse_addr_filter(event, filter_str, &filters);
if (ret)
return ret;
--
2.9.3
next reply other threads:[~2017-02-03 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 22:18 Andi Kleen [this message]
2017-02-03 22:18 ` [PATCH 2/2] perf tools: Support end symbols with no size for filters Andi Kleen
2017-02-06 13:15 ` Adrian Hunter
2017-02-09 22:59 ` Andi Kleen
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=20170203221830.22354-1-andi@firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--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