Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263307AbTEIQds (ORCPT ); Fri, 9 May 2003 12:33:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263315AbTEIQds (ORCPT ); Fri, 9 May 2003 12:33:48 -0400 Received: from watch.techsource.com ([209.208.48.130]:35785 "EHLO techsource.com") by vger.kernel.org with ESMTP id S263307AbTEIQdp (ORCPT ); Fri, 9 May 2003 12:33:45 -0400 Message-ID: <3EBBDC54.7070109@techsource.com> Date: Fri, 09 May 2003 12:50:28 -0400 From: Timothy Miller User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Miles Bader 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> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 699 Lines: 23 Miles Bader wrote: > 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. > Sure, but probably the majority are using x86 which would be affected by some of the ideas we've talked about in this thread. - 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/