From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262378AbTEIIqN (ORCPT ); Fri, 9 May 2003 04:46:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262383AbTEIIqN (ORCPT ); Fri, 9 May 2003 04:46:13 -0400 Received: from TYO202.gate.nec.co.jp ([202.32.8.202]:31126 "EHLO TYO202.gate.nec.co.jp") by vger.kernel.org with ESMTP id S262378AbTEIIqM (ORCPT ); Fri, 9 May 2003 04:46:12 -0400 To: Timothy Miller Cc: root@chaos.analogic.com, Roland Dreier , Linux kernel Subject: Re: top stack (l)users for 2.5.69 References: <20030507132024.GB18177@wohnheim.fh-wedel.de> <20030507135657.GC18177@wohnheim.fh-wedel.de> <52k7d2pqwm.fsf@topspin.com> <52bryeppb3.fsf@topspin.com> <52n0hyo85x.fsf@topspin.com> <3EB96FB2.2020401@techsource.com> <3EBA7AE2.9020401@techsource.com> Reply-To: Miles Bader System-Type: i686-pc-linux-gnu Blat: Foop From: Miles Bader Date: 09 May 2003 17:57:00 +0900 In-Reply-To: <3EBA7AE2.9020401@techsource.com> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Timothy Miller writes: > That is to say, some CPUs might have provision for a stack pointer to be > associated with each interrupt vector. On my arch, the CPU doesn't use the stack for interrupts at all... so any saving on the stack is what's done by entry.S. -Miles -- o The existentialist, not having a pillow, goes everywhere with the book by Sullivan, _I am going to spit on your graves_.