From: Rajagopal Ananthanarayanan <ananth@sgi.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: linux-mm@kvack.org
Subject: Re: page fault.
Date: Fri, 27 Oct 2000 10:38:58 -0700 [thread overview]
Message-ID: <39F9BDB2.8C0CFE94@sgi.com> (raw)
In-Reply-To: <8tboe4$3bfb7$1@fido.engr.sgi.com>
"Stephen C. Tweedie" wrote:
>
> Hi,
>
> On Thu, Oct 26, 2000 at 10:14:23PM -0400, afei@jhu.edu wrote:
> > You are right. I misunderstood what he wants. To know when the pagefault
> > occured, one simply can work on the pagefault handler. It is trivial.
>
> Page faults already produce a SIGSEGV which gets passed a sigcontext
> struct describing where the fault occurred.
>
Isn't it that only unsatisfied pagefaults generate
SIGSEGV? The original question was whether there
is a way to track all pagefaults in a given program.
Please correct if I'm wrong: the answer to this latter
question is no. Unless one modifies do_pagefault to
generate such a signal on all faults ...
--------------------------------------------------------------------------
Rajagopal Ananthanarayanan ("ananth")
Member Technical Staff, SGI.
--------------------------------------------------------------------------
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-10-27 17:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-26 15:52 ptes flags in compressed cache Rodrigo S. de Castro
2000-10-26 15:58 ` Stephen C. Tweedie
2000-10-27 2:12 ` page fault M.Jagadish Kumar
2000-10-26 19:45 ` afei
2000-10-26 19:53 ` Rik van Riel
2000-10-27 2:14 ` afei
2000-10-27 11:17 ` Stephen C. Tweedie
[not found] ` <8tboe4$3bfb7$1@fido.engr.sgi.com>
2000-10-27 17:38 ` Rajagopal Ananthanarayanan [this message]
2000-10-30 12:19 ` volodya
2000-10-27 7:59 ` ptes flags in compressed cache Christoph Rohland
[not found] <8ta1ir$358it$1@fido.engr.sgi.com>
2000-10-26 20:44 ` page fault Rajagopal Ananthanarayanan
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=39F9BDB2.8C0CFE94@sgi.com \
--to=ananth@sgi.com \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.com \
/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