From: Peter Zijlstra <peterz@infradead.org>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, vince@deater.net,
eranian@google.com, Arnaldo Carvalho de Melo <acme@infradead.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: Re: [PATCH v0 3/5] perf: Introduce instruction trace filtering
Date: Fri, 11 Dec 2015 16:12:29 +0100 [thread overview]
Message-ID: <20151211151229.GW6356@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1449840998-29902-4-git-send-email-alexander.shishkin@linux.intel.com>
On Fri, Dec 11, 2015 at 03:36:36PM +0200, Alexander Shishkin wrote:
> +/*
> + * Scan through mm's vmas and see if one of them matches the
> + * @filter; if so, adjust filter's address range.
> + * Called with mm::mmap_sem down for reading.
> + */
> +static int perf_itrace_filter_apply(struct perf_event *event,
> + struct perf_itrace_filter *filter,
> + struct mm_struct *mm)
> +{
> + struct vm_area_struct *vma;
lockdep_assert_held(&mm->mmap_sem);
If you want to be pedantic we could add:
lockdep_assert_held_shared()
lockdep_assert_held_exclusive()
to assert we hold it in any particular state.
> +
> + for (vma = mm->mmap; vma->vm_next; vma = vma->vm_next) {
> + struct file *file = vma->vm_file;
> + unsigned long off = vma->vm_pgoff << PAGE_SHIFT;
> + unsigned long vma_size = vma->vm_end - vma->vm_start;
> +
> + if (!file)
> + continue;
> +
> + if (!perf_itrace_filter_match(filter, file, off,
> + vma_size))
> + continue;
> +
> + filter->start = vma->vm_start + filter->offset;
> + filter->end = vma->vm_start + filter->offset +
> + filter->size;
> +
> + return 1;
> + }
> +
> + return 0;
> +}
next prev parent reply other threads:[~2015-12-11 15:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 13:36 [PATCH v0 0/5] perf: Introduce instruction trace filtering Alexander Shishkin
2015-12-11 13:36 ` [PATCH v0 1/5] perf: Move set_filter() from behind EVENT_TRACING Alexander Shishkin
2015-12-11 13:36 ` [PATCH v0 2/5] perf: Extend perf_event_aux() to optionally iterate through more events Alexander Shishkin
2015-12-11 13:36 ` [PATCH v0 3/5] perf: Introduce instruction trace filtering Alexander Shishkin
2015-12-11 14:02 ` Peter Zijlstra
2015-12-11 14:20 ` Alexander Shishkin
2015-12-11 14:23 ` Mark Rutland
2015-12-11 14:52 ` Peter Zijlstra
2015-12-11 15:12 ` Alexander Shishkin
2015-12-11 14:56 ` Peter Zijlstra
2015-12-11 15:14 ` Alexander Shishkin
2015-12-11 15:00 ` Peter Zijlstra
2015-12-11 15:17 ` Alexander Shishkin
2015-12-11 15:34 ` Peter Zijlstra
2015-12-11 16:06 ` Alexander Shishkin
2015-12-11 15:02 ` Peter Zijlstra
2015-12-11 15:20 ` Peter Zijlstra
2015-12-11 15:27 ` Alexander Shishkin
2015-12-11 15:33 ` Peter Zijlstra
2015-12-11 15:48 ` Alexander Shishkin
2015-12-11 16:01 ` Peter Zijlstra
2015-12-11 17:02 ` Peter Zijlstra
2015-12-11 15:09 ` Peter Zijlstra
2015-12-11 15:12 ` Peter Zijlstra [this message]
2015-12-11 15:28 ` Peter Zijlstra
2015-12-11 17:00 ` Peter Zijlstra
2015-12-11 17:13 ` Alexander Shishkin
2015-12-11 22:39 ` Peter Zijlstra
2015-12-11 16:59 ` Peter Zijlstra
2015-12-11 17:15 ` Alexander Shishkin
2015-12-11 18:11 ` Mathieu Poirier
2015-12-11 22:41 ` Peter Zijlstra
2015-12-11 13:36 ` [PATCH v0 4/5] perf/x86/intel/pt: IP filtering register/cpuid bits Alexander Shishkin
2015-12-11 13:36 ` [PATCH v0 5/5] perf/x86/intel/pt: Add support for instruction trace filtering in PT Alexander Shishkin
2015-12-11 18:06 ` Mathieu Poirier
2015-12-11 21:38 ` [PATCH v0 0/5] perf: Introduce instruction trace filtering Mathieu Poirier
2015-12-14 8:50 ` Alexander Shishkin
2015-12-15 0:25 ` 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=20151211151229.GW6356@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@infradead.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=vince@deater.net \
/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.