From: "H. Peter Anvin" <hpa@zytor.com>
To: Kanoj Sarcar <kanojsarcar@yahoo.com>
Cc: Linux MM mailing list <linux-mm@kvack.org>
Subject: Re: More questions...
Date: Mon, 15 Oct 2001 15:02:30 -0700 [thread overview]
Message-ID: <3BCB5CF6.5020607@zytor.com> (raw)
In-Reply-To: <20011015215654.16878.qmail@web14304.mail.yahoo.com>
Kanoj Sarcar wrote:
>
>>b) Is there an architecture-independent way to
>>determine if a page fault
>>was due to a read or write operation? On i386 I can
>>look at the %cr2
>>value in the sigcontext, but I'd prefer to do
>>something less arch-specific...
>>
>
> The last parameter to handle_mm_fault() ...
>
How do I determine it *in userspace*?
-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/
next prev parent reply other threads:[~2001-10-15 22:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-15 21:46 H. Peter Anvin
2001-10-15 21:56 ` Kanoj Sarcar
2001-10-15 22:02 ` H. Peter Anvin [this message]
2001-10-15 22:08 ` Andi Kleen
2001-10-15 22:11 ` H. Peter Anvin
2001-10-15 22:15 ` Andi Kleen
2001-10-15 22:31 ` H. Peter Anvin
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=3BCB5CF6.5020607@zytor.com \
--to=hpa@zytor.com \
--cc=kanojsarcar@yahoo.com \
--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