From: alan@lxorguk.ukuu.org.uk (Alan Cox)
To: hppa-linux@thepuffingroup.com
Subject: Re: [hppa-linux] Picky details of TLB fault handlers
Date: Mon, 22 Mar 1999 18:12:34 +0000 (GMT) [thread overview]
Message-ID: <m10P9Bi-0007U1C@the-village.bc.nu> (raw)
In-Reply-To: <199903221705.LAA01108@helgaaspc.rsn.hp.com> from "Bjorn Helgaas" at Mar 22, 99 11:05:09 am
> HP-UX does exactly this sort of thing for handling many traps and
> interrupts. It is fairly expensive, though, since you have to have
> a stack on which to save the IPSW/IIAQ and probably a bunch of other
> registers, and it's too much messing around for a TLB miss.
I'm right in assuming its legal to swap the return address - so the TLB
handler can do a short piece of TLB handling for a present page miss,
then stash the return into the kernel stack and rfi into the page fault handler
so it will in turn return to the user context ?
Alan
next prev parent reply other threads:[~1999-03-22 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-22 17:05 [hppa-linux] Picky details of TLB fault handlers Bjorn Helgaas
1999-03-22 18:12 ` Alan Cox [this message]
1999-03-22 17:41 ` Michael Shalayeff
-- strict thread matches above, loose matches on Subject: below --
1999-03-22 19:09 Bjorn Helgaas
1999-03-22 14:11 Christopher Neufeld
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=m10P9Bi-0007U1C@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=hppa-linux@thepuffingroup.com \
/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.