From: Matthew Wilcox <willy@debian.org>
To: Grant Grundler <grundler@dsl2.external.hp.com>
Cc: Matthew Wilcox <willy@debian.org>,
Randolph Chung <tausq@debian.org>,
John David Anglin <dave@hiauly1.hia.nrc.ca>,
carlos@baldric.uwo.ca, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: Trap handler
Date: Mon, 9 Dec 2002 18:55:21 +0000 [thread overview]
Message-ID: <20021209185521.M20336@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20021209184125.GC6635@dsl2.external.hp.com>; from grundler@dsl2.external.hp.com on Mon, Dec 09, 2002 at 11:41:25AM -0700
On Mon, Dec 09, 2002 at 11:41:25AM -0700, Grant Grundler wrote:
> As jsm agreed, if interrupts were disabled when we took the fault,
> we can't re-enable them while handling a page fault.
> Where x86 disables interrupts seems ok to me.
um, there's a difference between a page fault and a TLB miss. if you
have interrupts disabled and you take a page fault, something's gone
horribly wrong. having interrupts disabled when you miss the TLB cache
is no big deal. we _absolutely must not_ tamper with interrupt enable
state when handling a TLB miss.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2002-12-09 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021208232601.GH21187@tausq.org>
2002-12-08 23:55 ` [parisc-linux] Re: Trap handler John David Anglin
2002-12-09 5:12 ` Randolph Chung
2002-12-09 6:19 ` Randolph Chung
2002-12-09 12:54 ` Matthew Wilcox
2002-12-09 18:03 ` Grant Grundler
2002-12-09 18:20 ` Matthew Wilcox
2002-12-09 18:41 ` Grant Grundler
2002-12-09 18:55 ` Matthew Wilcox [this message]
2002-12-09 16:18 ` John David Anglin
2002-12-09 16:31 ` John David Anglin
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=20021209185521.M20336@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=carlos@baldric.uwo.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=grundler@dsl2.external.hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tausq@debian.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