From: Alexis Berlemont <alexis.berlemont@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Alexis Berlemont <alexis.berlemont@gmail.com>,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com
Subject: [PATCH v2] perf, x86-mm: declare page-faults tracepoints like irq-vectors ones
Date: Fri, 28 Oct 2016 01:31:33 +0200 [thread overview]
Message-ID: <20161027233134.12117-1-alexis.berlemont@gmail.com> (raw)
In-Reply-To: <20161027083714.GF3568@worktop.programming.kicks-ass.net>
So, would you be OK with the following patch ?
There is a symmetry just like irq_vectors tracepoints:
# perf list | grep -E "exception|irq_vectors"
exceptions:page_fault_kernel_entry [Tracepoint event]
exceptions:page_fault_kernel_exit [Tracepoint event]
exceptions:page_fault_user_entry [Tracepoint event]
exceptions:page_fault_user_exit [Tracepoint event]
irq_vectors:call_function_entry [Tracepoint event]
irq_vectors:call_function_exit [Tracepoint event]
...
Maybe 2 tracepoints (instead of 4) should have been enough; however,
there were already 1 tracepoint per mode before.
Alexis.
Alexis Berlemont (1):
perf, x86-mm: declare page-faults tracepoints like irq-vectors ones
arch/x86/include/asm/trace/exceptions.h | 17 ++++++++++++++++-
arch/x86/mm/fault.c | 17 ++++++++++++++---
2 files changed, 30 insertions(+), 4 deletions(-)
--
2.10.1
next prev parent reply other threads:[~2016-10-27 23:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 23:51 [PATCH 0/2] perf: measure page fault duration in perf trace Alexis Berlemont
2016-10-25 23:51 ` [PATCH 1/2] perf, x86-mm: Add exit-fault tracing Alexis Berlemont
2016-10-26 8:51 ` Peter Zijlstra
2016-10-26 18:53 ` Arnaldo Carvalho de Melo
2016-10-27 8:37 ` Peter Zijlstra
2016-10-27 23:31 ` Alexis Berlemont [this message]
2016-10-27 23:31 ` [PATCH v2] perf, x86-mm: declare page-faults tracepoints like irq-vectors ones Alexis Berlemont
2016-11-18 0:21 ` [PATCH v3 0/2] perf: measure page fault duration in perf trace Alexis Berlemont
2016-12-05 23:40 ` Alexis Berlemont
2016-12-06 14:46 ` Arnaldo Carvalho de Melo
2016-11-18 0:21 ` [PATCH v3 1/2] perf, x86-mm: declare page-faults tracepoints like irq-vectors ones Alexis Berlemont
2016-11-18 0:21 ` [PATCH v3 2/2] perf: add page fault duration measures in perf trace Alexis Berlemont
2016-10-27 8:38 ` [PATCH 1/2] perf, x86-mm: Add exit-fault tracing Peter Zijlstra
2016-10-25 23:52 ` [PATCH 2/2] perf: add page fault duration measures in perf trace Alexis Berlemont
2016-10-26 8:46 ` [PATCH 0/2] perf: measure page fault duration " Peter Zijlstra
2016-10-26 18:47 ` Arnaldo Carvalho de Melo
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=20161027233134.12117-1-alexis.berlemont@gmail.com \
--to=alexis.berlemont@gmail.com \
--cc=acme@kernel.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;
as well as URLs for NNTP newsgroup(s).