From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] psr.dt state when DO_SAVE_MIN is invoked
Date: Wed, 06 Mar 2002 19:45:38 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905232@msgid-missing> (raw)
Some systems running an old kernel (2.4.7) have been seen to
hang looping in an apparent recursive TLB fault. The same tests
that locked up these machines seem to run fine on new kernels,
but while looking into the issue the following oddity was
noted in the code, that still exists in 2.4.18
in arch/ia64/kernel/ivt.S we have:
ENTRY(page_fault)
ssm psr.dt
;;
srlz.i
;;
SAVE_MIN_WITH_COVER
and minstate.h defines:
#define SAVE_MIN_WITH_COVER DO_SAVE_MIN(cover, mov rCRIFS=cr.ifs,)
which in turn says:
/*
* DO_SAVE_MIN switches to the kernel stacks (if necessary) and saves
* the minimum state necessary that allows us to turn psr.ic back
* on.
*
* Assumed state upon entry:
* psr.ic: off
* psr.dt: off
* r31: contains saved predicates (pr)
*
...
See how page_fault explicitly sets psr.dt, and then invokes a macro
that says that the assumed entry state is psr.dt should be off. Is
the comment just plain wrong, or is there a potential issue here?
The 2.4.7 failure hits at around the 67 hour mark in the tests, the
newer (RedHat 7.2 a.k.a. 2.4.9-18) kernel survives 72 hours ... but
that's as long as we scheduled the test to run.
-Tony
next reply other threads:[~2002-03-06 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 19:45 Luck, Tony [this message]
2002-03-06 20:22 ` [Linux-ia64] psr.dt state when DO_SAVE_MIN is invoked David Mosberger
2002-03-06 20:59 ` Fleckenstein, Chuck
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-105590701905232@msgid-missing \
--to=tony.luck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox