RE: [Linux-ia64] determining read or write on a page fault

["Neelakantam, NaveenX" <naveenx.neelakantam@intel.com>]

Not at the moment.  :-)

We are looking into it.

Naveen

-----Original Message-----
From: David Mosberger [mailto:davidm@napali.hpl.hp.com]
Sent: Thursday, April 04, 2002 3:59 PM
To: Hoeflinger, Jay P
Cc: 'davidm@hpl.hp.com'; linux-ia64@linuxia64.org; Neelakantam, NaveenX
Subject: RE: [Linux-ia64] determining read or write on a page fault


>>>>> On Wed, 3 Apr 2002 08:18:45 -0800 , "Hoeflinger, Jay P"
<jay.p.hoeflinger@intel.com> said:

  Jay> We want to report success using the 2.4.18 kernel and the info
  Jay> sent to the segv handler on a page fault for our distributed
  Jay> virtual shared memory system on IA64.

Great!  Glad to hear that.

  Jay> We had to make one assumption, though, that wasn't covered in
  Jay> your mail (below).

  Jay> The assumption was that if si_code=0, that the access was a
  Jay> "read".  We had originally assumed it was a "write", but this
  Jay> caused some errors.  When we changed to assuming "read", things
  Jay> worked.  Is this assumption valid?  When does this case occur?
  Jay> Our scan of the kernel source seemed to indicate that this case
  Jay> can't happen.

Hmmh, that's a bit odd.  If si_code is zero, we can't know what
triggered the segfault.  It could have been a read, a write, a
semaphore instruction, or something entirely different (e.g., user
sending SIGSEGV via kill(2)).  Now, for a distributed shared memory
system, I'd have thought that you'd want to treat such unknown
accesses as writes, because otherwise the fault might re-occur as soon
as the faulting instruction is restarted (since the page still doesn't
have write permission).  For normal cases (non-error cases/silly user
cases), I wouldn't have expected this to occur.  Do you know where
those SIGSEGVs with si_code=0 were coming from?

	--david