Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264221AbTEGU0L (ORCPT ); Wed, 7 May 2003 16:26:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264243AbTEGU0L (ORCPT ); Wed, 7 May 2003 16:26:11 -0400 Received: from watch.techsource.com ([209.208.48.130]:32421 "EHLO techsource.com") by vger.kernel.org with ESMTP id S264221AbTEGU0K (ORCPT ); Wed, 7 May 2003 16:26:10 -0400 Message-ID: <3EB96FB2.2020401@techsource.com> Date: Wed, 07 May 2003 16:42:26 -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: root@chaos.analogic.com CC: 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> 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: 822 Lines: 21 Richard B. Johnson wrote: > > When a caller executes int 0x80, this is a software interrupt, > called a 'trap'. It enters the trap handler on the kernel stack, > with the segment selectors set up as defined for that trap-handler. > It happens because software told hardware what to do ahead of time. > Software doesn't do it during the trap event. In the trap handler, > no context switch normally occurs. On typical processors, when one gets an interrupt, the current program counter and processor state flags are pushed onto a stack. Which stack gets used for this? - 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/