From: "Sam Varshavchik" <mrsam@courier-mta.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Recursive deadlock on die_lock
Date: Mon, 15 Oct 2001 01:55:20 GMT [thread overview]
Message-ID: <courier.3BCA4208.000047A1@ny.email-scan.com> (raw)
In-Reply-To: <fa.k3c2fuv.1q26ra4@ifi.uio.no> <fa.idkv82v.3jcuip@ifi.uio.no>
In-Reply-To: <fa.idkv82v.3jcuip@ifi.uio.no>
Keith Owens writes:
> On 14 Oct 2001 17:14:24 -0600,
> ebiederm@xmission.com (Eric W. Biederman) wrote:
>>Keith Owens <kaos@ocs.com.au> writes:
>>> IA64 also has PAL code which is
>>> called directly by the kernel, that PAL code has no unwind data so
>>> failures in PAL code result in bad or incomplete back traces.
>>
>>PAL Ahh!!!!!
>>
>>Please tell me that we are not rely on the firmware to be correct
>>after we have finished initializing the operating system.
>>
>>Please tell me it ain't so. I have nightmares about that kind of setup.
>
> Not only do we rely on it, it is mandated by the IA64 design. Intel
> IA64 System Abstraction Layer, 24535901.pdf. The IA64 kernel calls SAL
> all over the place. grep -ir '\<[ps]al' include/asm-ia64/ arch/ia64/
Oh, goody! What an excellent way to shove CPRM or SSSCA down your throat!
The possibilities are endless...
--
Sam
next parent reply other threads:[~2001-10-15 1:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.k3c2fuv.1q26ra4@ifi.uio.no>
[not found] ` <fa.idkv82v.3jcuip@ifi.uio.no>
2001-10-15 1:55 ` Sam Varshavchik [this message]
2001-10-14 4:25 Keith Owens
2001-10-14 6:42 ` Andrew Morton
2001-10-14 7:13 ` Keith Owens
2001-10-14 23:14 ` Eric W. Biederman
2001-10-15 0:42 ` 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=courier.3BCA4208.000047A1@ny.email-scan.com \
--to=mrsam@courier-mta.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®