All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Fremlin <vii@users.sourceforge.net>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: VM tuning through fault trace gathering [with actual code]
Date: 26 Jun 2001 16:38:07 +0100	[thread overview]
Message-ID: <m2vgljb6ao.fsf@boreas.yi.org.> (raw)
In-Reply-To: <Pine.LNX.4.21.0106261031150.850-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0106261031150.850-100000@freak.distro.conectiva> (Marcelo Tosatti's message of "Tue, 26 Jun 2001 10:52:16 -0300 (BRT)")

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.

-- 

	http://ape.n3.net

WARNING: multiple messages have this Message-ID (diff)
From: John Fremlin <vii@users.sourceforge.net>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: VM tuning through fault trace gathering [with actual code]
Date: 26 Jun 2001 16:38:07 +0100	[thread overview]
Message-ID: <m2vgljb6ao.fsf@boreas.yi.org.> (raw)
In-Reply-To: <Pine.LNX.4.21.0106261031150.850-100000@freak.distro.conectiva> (Marcelo Tosatti's message of "Tue, 26 Jun 2001 10:52:16 -0300 (BRT)")

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.

-- 

	http://ape.n3.net
--
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-26 15:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-25 15:26 VM tuning through fault trace gathering [with actual code] John Fremlin
2001-06-25 15:26 ` John Fremlin
2001-06-25 17:57 ` Rik van Riel
2001-06-25 17:57   ` Rik van Riel
2001-06-25 21:15   ` John Fremlin
2001-06-25 21:15     ` John Fremlin
2001-06-25 21:33     ` EXT2 Filesystem permissions (bug)? Shawn Starr
2001-06-25 21:42       ` H. Peter Anvin
2001-06-25 22:20         ` Shawn Starr
2001-06-26 22:23         ` Kenneth Johansson
2001-06-26 22:40           ` Hua Zhong
2001-06-26 23:04           ` Albert D. Cahalan
2001-06-27  0:02           ` Guest section DW
2001-06-27  9:37           ` Luigi Genoni
2001-06-25 21:47       ` Andreas Dilger
2001-06-25 22:10       ` Luigi Genoni
2001-06-26 14:02     ` VM tuning through fault trace gathering [with actual code] Scott F. Kaplan
2001-06-26 19:29       ` John Fremlin
2001-06-26  0:53 ` Marcelo Tosatti
2001-06-26  0:53   ` Marcelo Tosatti
2001-06-26 12:54   ` John Fremlin
2001-06-26 12:54     ` John Fremlin
2001-06-26 13:52     ` Marcelo Tosatti
2001-06-26 13:52       ` Marcelo Tosatti
2001-06-26 15:38       ` John Fremlin [this message]
2001-06-26 15:38         ` John Fremlin
2001-06-27 10:09         ` Marcelo Tosatti
2001-06-27 10:09           ` Marcelo Tosatti
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=m2vgljb6ao.fsf@boreas.yi.org. \
    --to=vii@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marcelo@conectiva.com.br \
    /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.