From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: John Fremlin <vii@users.sourceforge.net>
Cc: linux-mm@kvack.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: VM tuning through fault trace gathering [with actual code]
Date: Wed, 27 Jun 2001 07:09:14 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.21.0106270707550.1291-100000@freak.distro.conectiva> (raw)
In-Reply-To: <m2vgljb6ao.fsf@boreas.yi.org.>
On 26 Jun 2001, John Fremlin wrote:
> Marcelo Tosatti <marcelo@conectiva.com.br> writes:
>
> > ####################################################################
> > Event Time PID Length Description
> > ####################################################################
> >
> > Trap entry 991,299,585,597,016 678 12 TRAP: page fault; EIP : 0x40067785
>
> That looks like just the generic interrupt handling. It does not do
> what I want to do, i.e. record some more info about the fault saying
> where it comes from.
You can create custom events with LTT and then you can get them from a
"big buffer" to userlevel later, then.
I just told you about LTT because I think you are redoing work by creating
the tracing facilities...
--
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/
next prev parent reply other threads:[~2001-06-27 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 15:26 John Fremlin
2001-06-25 17:57 ` Rik van Riel
2001-06-25 21:15 ` John Fremlin
2001-06-26 14:02 ` Scott F. Kaplan
2001-06-26 19:29 ` John Fremlin
2001-06-26 0:53 ` Marcelo Tosatti
2001-06-26 12:54 ` John Fremlin
2001-06-26 13:52 ` Marcelo Tosatti
2001-06-26 15:38 ` John Fremlin
2001-06-27 10:09 ` Marcelo Tosatti [this message]
2001-06-27 12:47 ` Scott F. Kaplan
2001-06-27 13:51 ` Marcelo Tosatti
2001-06-27 16:05 ` John Fremlin
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=Pine.LNX.4.21.0106270707550.1291-100000@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vii@users.sourceforge.net \
/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