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 0/2] perf: measure page fault duration in perf trace
Date: Wed, 26 Oct 2016 01:51:58 +0200 [thread overview]
Message-ID: <20161025235200.28781-1-alexis.berlemont@gmail.com> (raw)
Hi,
Here are 2 small patches which try to fulfill a point in the perf todo
list:
* Forward port the page fault tracepoints and use it in 'trace'.
http://git.kernel.org/?p=linux/kernel/git/acme/linux.git;a=commitdiff;h=d53b11976093b6d8afeb8181db53aaffc754920d;hp=32ba4abf60ae1b710d22a75725491815de649bc5
There are some questionable points:
* With luck I think I found the patch related with the todo item (the
link in the todo wiki page is broken); I hope I am not wrong...
* In the patch mentioned above, I found only changes related with
tracepoints creations and calls; the tracepoints were declared
generic (in include/trace/events/kmem.h) but were only called in x86
(arch/x86/mm/fault.c); as in x86, the tracepoint
"mm_pagefault_start" looks fairly like "page_fault_user" and
"page_fault_kernel", I decided to only create one x86-specific
tracepoint: "page_fault_exit"; maybe, you would prefer declaring
generic tracepoints;
* No option has been added for activating page-fault duration
calculation: if the needed tracepoints are available, durations will
be printed; maybe, that was not what you were looking for.
The patches were generated against tip/perf/core.
Alexis.
Alexis Berlemont (2):
perf, x86-mm: Add exit-fault tracing
perf: add page fault duration measures in perf trace
arch/x86/include/asm/trace/exceptions.h | 21 +++
arch/x86/mm/fault.c | 1 +
tools/perf/builtin-trace.c | 225 ++++++++++++++++++++++++++++----
3 files changed, 221 insertions(+), 26 deletions(-)
--
2.10.1
next reply other threads:[~2016-10-25 23:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 23:51 Alexis Berlemont [this message]
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 ` [PATCH v2] perf, x86-mm: declare page-faults tracepoints like irq-vectors ones Alexis Berlemont
2016-10-27 23:31 ` 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=20161025235200.28781-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).