From: David Mosberger-Tang <David.Mosberger@acm.org>
To: linux-ia64@vger.kernel.org
Subject: Re: MCA/INIT: need to wire CURRENT_STACK?
Date: Wed, 21 Sep 2005 18:12:58 +0000 [thread overview]
Message-ID: <ed5aea4305092111125edcf7d4@mail.gmail.com> (raw)
In-Reply-To: <16451.1127265127@ocs3.ocs.com.au>
> BUT ... it raises the question of whether you will do anything
> in your MCA handler that will run into problems because the stack
> is perhaps[1] not pinned ... just mapped by a DTC entry. I forget
> what the exact issue is that led to pinning the stack with DTR[2],
> but there is a correctness issue involved. David: memory jog time??
Any virtually mapped memory that needs to be accessed with PSR.IC=0
needs to be pinned because otherwise you'd get a nested TLB fault and
things would go south from there real fast.
--david
--
Mosberger Consulting LLC, voice/fax: 510-744-9372,
http://www.mosberger-consulting.com/
35706 Runckel Lane, Fremont, CA 94536
next prev parent reply other threads:[~2005-09-21 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 1:12 MCA/INIT: need to wire CURRENT_STACK? Keith Owens
2005-09-21 17:47 ` Luck, Tony
2005-09-21 18:12 ` David Mosberger-Tang [this message]
2005-09-21 22:58 ` Keith Owens
2005-09-21 23:09 ` David Mosberger-Tang
2005-09-21 23:21 ` Keith Owens
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=ed5aea4305092111125edcf7d4@mail.gmail.com \
--to=david.mosberger@acm.org \
--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