linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Scott F. Kaplan <sfkaplan@cs.amherst.edu>
To: linux-mm@kvack.org
Subject: Re: VM tuning through fault trace gathering [with actual code]
Date: Wed, 27 Jun 2001 08:47:47 -0400	[thread overview]
Message-ID: <0106270847470D.01124@spigot> (raw)
In-Reply-To: <Pine.LNX.4.21.0106270707550.1291-100000@freak.distro.conectiva>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 27 June 2001 06:09 am, Marcelo Tosatti wrote:
> 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 guess that i have a different concern with this existing utility.  It seems 
that it will report page faults (minor or major) for the normal VM system 
configuration.  What if we want it to record all (or nearly) all page 
references, even ones to pages that *normally* wouldn't cause any kind of 
interrupt?  That ability seems new and unique to John's utility.

(I know, I need to read the LLT manual, as it may be able to do exactly what 
I'm describing.  However, I don't think that's the case.)

Scott
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7OdX28eFdWQtoOmgRAlhHAKCFHjgw62OlQmytkRiY+Zl9xaMz7gCfXSmm
mNsg0QUAwAhJnhwrL088IwI=
=CC+e
-----END PGP SIGNATURE-----
--
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/

  reply	other threads:[~2001-06-27 12:47 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
2001-06-27 12:47           ` Scott F. Kaplan [this message]
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=0106270847470D.01124@spigot \
    --to=sfkaplan@cs.amherst.edu \
    --cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox