From: Jiri Olsa <jolsa@redhat.com>
To: mingo@elte.hu, rostedt@goodmis.org, andi@firstfloor.org,
lwoodman@redhat.com, hch@infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCHv2 0/2] tracing,mm - add kernel pagefault tracepoint for x86 & x86_64
Date: Thu, 11 Nov 2010 10:09:07 +0100 [thread overview]
Message-ID: <1289466549-7602-1-git-send-email-jolsa@redhat.com> (raw)
In-Reply-To: <20101110164413.GA5360@nowhere>
This provides a tracepoint to trace kernel pagefault event
for x86 and x86_64 architectures.
There's a problem with this tracepoint when having the
userstacktrace option enabled, since it might generated
the page fault itself. The 1/2 patch address this issue.
v2 changes:
- replaced regs for error_code in page fault trace
- swapped the patch order not to introduce the regression
- minor code style change
attached patches:
1/2 tracing - fix recursive user stack trace
2/2 tracing,mm - add kernel pagefault tracepoint for x86 & x86_64
wbr,
jirka
---
arch/x86/mm/fault.c | 32 +++++++++++++++++++++-----------
include/trace/events/kmem.h | 22 ++++++++++++++++++++++
kernel/trace/trace.c | 17 +++++++++++++++++
3 files changed, 60 insertions(+), 11 deletions(-)
next prev parent reply other threads:[~2010-11-11 9:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 11:56 [PATCH 0/2] tracing,mm - add kernel pagefault tracepoint for x86 & x86_64 Jiri Olsa
2010-11-10 11:56 ` [PATCH 1/2] " Jiri Olsa
2010-11-10 13:29 ` Christoph Hellwig
2010-11-10 13:44 ` Jiri Olsa
2010-11-10 13:52 ` Ingo Molnar
2010-11-10 15:00 ` Frederic Weisbecker
2010-11-10 15:17 ` Jiri Olsa
2010-11-10 15:20 ` Christoph Hellwig
2010-11-10 16:28 ` Andi Kleen
2010-11-10 16:44 ` Frederic Weisbecker
2010-11-11 9:09 ` Jiri Olsa [this message]
2010-11-11 9:09 ` [PATCHv2 1/2] tracing - fix recursive user stack trace Jiri Olsa
2010-11-11 10:34 ` Andi Kleen
2010-11-11 9:09 ` [PATCHv2 2/2] tracing,mm - add kernel pagefault tracepoint for x86 & x86_64 Jiri Olsa
2010-11-11 12:51 ` Christoph Hellwig
2010-11-11 13:15 ` Jiri Olsa
2010-11-15 13:43 ` Frederic Weisbecker
2010-11-15 14:06 ` Andi Kleen
2010-11-15 14:54 ` Frederic Weisbecker
2010-11-15 15:04 ` Steven Rostedt
2010-11-15 14:19 ` Steven Rostedt
2010-11-16 9:23 ` Jiri Olsa
2010-11-16 13:13 ` Steven Rostedt
2010-11-10 11:56 ` [PATCH 2/2] tracing - fix recursive user stack trace Jiri Olsa
2010-11-11 0:13 ` Li Zefan
2010-11-11 21:57 ` Steven Rostedt
2010-11-18 14:05 ` [tip:perf/core] tracing: Fix " tip-bot for Steven Rostedt
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=1289466549-7602-1-git-send-email-jolsa@redhat.com \
--to=jolsa@redhat.com \
--cc=andi@firstfloor.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lwoodman@redhat.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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.