public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hoeflinger, Jay P" <jay.p.hoeflinger@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] determining read or write on a page fault
Date: Thu, 21 Feb 2002 21:09:30 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905163@msgid-missing> (raw)

We are writing software that handles page faults on an Itanium system, and
so have registered a SIGSEGV
handler.  We think we know how to determine the address being referenced,
but don't know how to determine
whether the access was a read or a write.

We believe that the handler entry point should be:

void
segv_handler(
        int                  sig,
       siginfo_t *sip, 
        struct sigcontext *scp)

and the address of the access therefore should be:

((caddr_t)sip->si_addr)

but how do we determine READ vs WRITE?

In IA-32 linux, we could check the PF_ERR bit.  Is there an equivalent for
IA-64?

Thanks

Naveen Neelakantam and Jay Hoeflinger


Jay Hoeflinger, jay.p.hoeflinger@intel.com
KAI Software, A Division of Intel Americas, Inc., http://www.kai.com
Phone 217/356-2288, Direct 217/356-5052 x 140, Fax 217/356-5199




             reply	other threads:[~2002-02-21 21:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21 21:09 Hoeflinger, Jay P [this message]
2002-02-21 21:57 ` [Linux-ia64] determining read or write on a page fault Boehm, Hans
2002-02-22 15:58 ` Hoeflinger, Jay P
2002-02-22 17:06 ` David Mosberger
2002-02-22 17:27 ` Hoeflinger, Jay P
2002-02-22 17:29 ` n0ano
2002-02-22 18:45 ` David Mosberger
2002-02-23  1:24 ` David Mosberger
2002-02-25 17:07 ` Hoeflinger, Jay P
2002-02-25 18:36 ` David Mosberger
2002-04-03 16:18 ` Hoeflinger, Jay P
2002-04-04 21:59 ` David Mosberger
2002-04-04 22:49 ` Neelakantam, NaveenX
2002-04-14 22:08 ` Neelakantam, NaveenX
2002-04-15 16:55 ` David Mosberger
2002-04-16 20:18 ` Neelakantam, NaveenX

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=marc-linux-ia64-105590701905163@msgid-missing \
    --to=jay.p.hoeflinger@intel.com \
    --cc=linux-ia64@vger.kernel.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