From: Andi Kleen <andi@firstfloor.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
mingo@elte.hu, rostedt@goodmis.org, andi@firstfloor.org,
lwoodman@redhat.com, hch@infradead.org,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCHv2 2/2] tracing,mm - add kernel pagefault tracepoint for x86 & x86_64
Date: Mon, 15 Nov 2010 15:06:33 +0100 [thread overview]
Message-ID: <20101115140632.GI7269@basil.fritz.box> (raw)
In-Reply-To: <20101115134325.GA5410@nowhere>
> Actually I don't see any reason right now to trace only kernel faults. Do you?
> If that's needed, one can still check on post-processing that the address
> was in the kernel.
I think the idea is to get more context on oopses. If the event only covers
that the overhead in the common case (minus *_user) is much less,
versus the more generalized points you use.
For tracing the whole page fault me think it's better to have
a generalized exception tracer with a filter on page fault.
-Andi
next prev parent reply other threads:[~2010-11-15 14:06 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 ` [PATCHv2 0/2] " Jiri Olsa
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 [this message]
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=20101115140632.GI7269@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=fweisbec@gmail.com \
--cc=hch@infradead.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwoodman@redhat.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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.