All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hoeflinger, Jay P" <jay.p.hoeflinger@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] mprotect problem
Date: Fri, 07 Dec 2001 16:23:32 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805644@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805634@msgid-missing>

I don't know how to do this.  I'm not a kernel hacker and I've
never rebuilt the kernel.

Is there any way I can view this with a debugger or anything else?

Jay

-----Original Message-----
From: David Mosberger [mailto:davidm@hpl.hp.com]
Sent: Friday, December 07, 2001 10:10 AM
To: Hoeflinger, Jay P
Cc: 'Boehm, Hans'; 'n0ano@indstorage.com'; MOSBERGER, DAVID
(HP-PaloAlto,unix3); 'linux-ia64@linuxia64.org'
Subject: RE: [Linux-ia64] mprotect problem


>>>>> On Fri, 7 Dec 2001 06:53:14 -0800 , "Hoeflinger, Jay P"
<jay.p.hoeflinger@intel.com> said:

  Jay> No, we haven't checked that this is not a page size or
  Jay> alignment issue.  The page size we get from getpagesize().

Can you find out *why* the later page faults occur?  Printing the ISR
should help.  The page fault handler does not (yet) setup si_isr in
the siginfo, but you could just hack
arch/ia64/mm/fault.c:ia64_do_page_fault() to print the ISR when you
detect the problematic case.

If you have a (small) test program that replicates the problem, I'd be
happy to look into it early next week.

	--david


  parent reply	other threads:[~2001-12-07 16:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06 23:56 [Linux-ia64] mprotect problem Hoeflinger, Jay P
2001-12-07  0:11 ` n0ano
2001-12-07 14:53 ` Hoeflinger, Jay P
2001-12-07 15:13 ` n0ano
2001-12-07 15:18 ` Hoeflinger, Jay P
2001-12-07 16:10 ` David Mosberger
2001-12-07 16:23 ` Hoeflinger, Jay P [this message]
2001-12-07 17:34 ` David Mosberger
2001-12-07 19:47 ` Hoeflinger, Jay P
2001-12-07 20:13 ` Boehm, Hans
2001-12-07 20:27 ` David Mosberger

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-105590698805644@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 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.