All of lore.kernel.org
 help / color / mirror / Atom feed
From: credmonster@gmail.com (Chris Redmon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Add fault_major, fault_minor page fault trace events
Date: Wed, 12 Apr 2017 22:20:37 -0400	[thread overview]
Message-ID: <20170413022040.10156-1-credmonster@gmail.com> (raw)

These changes add common trace events for major and minor page faults,
as well as adding these traces to the arm and arm64 architectures. These
traces offer useful information for determining the source of page faults
in realtime systems, as well as the time penalty for taking a major or
minor page fault.

I made an attempt to minimize the overhead when these tracepoints are not
enabled, but I'm willing to make more changes if desired.

Chris Redmon (3):
  tracing: Introduce traces for major and minor page faults
  arm: Utilize trace events for major and minor page faults
  arm64: Utilize trace events for major and minor page faults

 arch/arm/mm/fault.c          | 14 +++++++
 arch/arm64/mm/fault.c        | 14 +++++++
 include/trace/events/fault.h | 87 ++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 115 insertions(+)
 create mode 100644 include/trace/events/fault.h

-- 
2.12.2.599.gcf11a67

             reply	other threads:[~2017-04-13  2:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13  2:20 Chris Redmon [this message]
2017-04-13  2:20 ` [PATCH 1/3] tracing: Introduce traces for major and minor page faults Chris Redmon
2017-04-13  2:20 ` [PATCH 2/3] arm: Utilize trace events " Chris Redmon
2017-04-13  2:20 ` [PATCH 3/3] arm64: " Chris Redmon
2017-04-25 16:49 ` [PATCH 0/3] Add fault_major, fault_minor page fault trace events Will Deacon

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=20170413022040.10156-1-credmonster@gmail.com \
    --to=credmonster@gmail.com \
    --cc=linux-arm-kernel@lists.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 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.