From: Matt Chapman <matthewc@cse.unsw.edu.au>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] sigaltstack and RBS
Date: Sun, 09 Feb 2003 05:19:20 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805824@msgid-missing> (raw)
I'm having some difficulty "demand paging" register backing store from
userspace (i.e. using SIGSEGV to map pages in on demand).
The problem is that even when using sigaltstack, the original backing
store (which caused the fault) is still touched when returning to the
signal trampoline, before it switches to the alternate RBS. Thus I
get recursive faulting before it gets to the signal handler.
Ideally, signal handling on an alternate RBS/stack wouldn't touch the
original RBS/stack at all.
Any suggestions how to deal with this?
Matt
next reply other threads:[~2003-02-09 5:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-09 5:19 Matt Chapman [this message]
2003-02-09 5:27 ` [Linux-ia64] sigaltstack and RBS David Mosberger
2003-02-09 5:47 ` Matt Chapman
2003-02-09 7:58 ` Matt Chapman
2003-02-09 8:48 ` David Mosberger
2003-02-09 10:55 ` Matt Chapman
2003-02-09 18:22 ` David Mosberger
2003-02-11 3:06 ` David Mosberger
2003-02-11 7:26 ` Matt Chapman
2003-02-11 19:11 ` David Mosberger
2003-03-07 23:35 ` Bjorn Helgaas
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-105590709805824@msgid-missing \
--to=matthewc@cse.unsw.edu.au \
--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