Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 14 Oct 2001 21:55:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 14 Oct 2001 21:54:56 -0400 Received: from mail.courier-mta.com ([66.92.103.29]:41427 "EHLO mail.courier-mta.com") by vger.kernel.org with ESMTP id ; Sun, 14 Oct 2001 21:54:49 -0400 In-Reply-To: In-Reply-To: From: "Sam Varshavchik" To: linux-kernel@vger.kernel.org Subject: Re: Recursive deadlock on die_lock Date: Mon, 15 Oct 2001 01:55:20 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-ID: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Keith Owens writes: > On 14 Oct 2001 17:14:24 -0600, > ebiederm@xmission.com (Eric W. Biederman) wrote: >>Keith Owens 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/