From: "H. Peter Anvin" <hpa@zytor.com>
To: "zhangwei(Jovi)" <jovi.zhangwei@huawei.com>
Cc: Francis Deslauriers <fdeslaur@gmail.com>,
linux-mm@kvack.org, tglx@linutronix.de, mingo@redhat.com,
x86@kernel.org, rostedt@goodmis.org, fweisbec@gmail.com,
raphael.beamonte@gmail.com, mathieu.desnoyers@efficios.com,
linux-kernel@vger.kernel.org
Subject: Re: [page fault tracepoint 1/2] Add page fault trace event definitions
Date: Thu, 09 May 2013 06:48:14 -0700 [thread overview]
Message-ID: <518BA91E.3080406@zytor.com> (raw)
In-Reply-To: <518B464E.6010208@huawei.com>
On 05/08/2013 11:46 PM, zhangwei(Jovi) wrote:
> On 2013/5/9 14:05, Francis Deslauriers wrote:
>> Add page_fault_entry and page_fault_exit event definitions. It will
>> allow each architecture to instrument their page faults.
>
> I'm wondering if this tracepoint could handle other page faults,
> like faults in kernel memory(vmalloc, kmmio, etc...)
>
> And if we decide to support those faults, add a type annotate in TP_printk
> would be much helpful for user, to let user know what type of page faults happened.
>
The plan for x86 was to switch the IDT so that any exception could get a
trace event without any overhead in normal operation. This has been in
the process for quite some time but looks like it was getting very close.
-hpa
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: "zhangwei(Jovi)" <jovi.zhangwei@huawei.com>
Cc: Francis Deslauriers <fdeslaur@gmail.com>,
linux-mm@kvack.org, tglx@linutronix.de, mingo@redhat.com,
x86@kernel.org, rostedt@goodmis.org, fweisbec@gmail.com,
raphael.beamonte@gmail.com, mathieu.desnoyers@efficios.com,
linux-kernel@vger.kernel.org
Subject: Re: [page fault tracepoint 1/2] Add page fault trace event definitions
Date: Thu, 09 May 2013 06:48:14 -0700 [thread overview]
Message-ID: <518BA91E.3080406@zytor.com> (raw)
In-Reply-To: <518B464E.6010208@huawei.com>
On 05/08/2013 11:46 PM, zhangwei(Jovi) wrote:
> On 2013/5/9 14:05, Francis Deslauriers wrote:
>> Add page_fault_entry and page_fault_exit event definitions. It will
>> allow each architecture to instrument their page faults.
>
> I'm wondering if this tracepoint could handle other page faults,
> like faults in kernel memory(vmalloc, kmmio, etc...)
>
> And if we decide to support those faults, add a type annotate in TP_printk
> would be much helpful for user, to let user know what type of page faults happened.
>
The plan for x86 was to switch the IDT so that any exception could get a
trace event without any overhead in normal operation. This has been in
the process for quite some time but looks like it was getting very close.
-hpa
next prev parent reply other threads:[~2013-05-09 13:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 6:05 [page fault tracepoint 1/2] Add page fault trace event definitions Francis Deslauriers
2013-05-09 6:05 ` Francis Deslauriers
2013-05-09 6:05 ` [page fault tracepoint 2/2] x86:Instruments page fault trace event Francis Deslauriers
2013-05-09 6:05 ` Francis Deslauriers
2013-05-09 6:46 ` [page fault tracepoint 1/2] Add page fault trace event definitions zhangwei(Jovi)
2013-05-09 6:46 ` zhangwei(Jovi)
2013-05-09 13:48 ` H. Peter Anvin [this message]
2013-05-09 13:48 ` H. Peter Anvin
2013-05-13 11:21 ` Mathieu Desnoyers
2013-05-13 11:21 ` Mathieu Desnoyers
2013-05-13 15:08 ` Steven Rostedt
2013-05-13 15:08 ` 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=518BA91E.3080406@zytor.com \
--to=hpa@zytor.com \
--cc=fdeslaur@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jovi.zhangwei@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=raphael.beamonte@gmail.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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.