From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11171 invoked by alias); 6 Jun 2007 10:33:53 -0000 Received: (qmail 11146 invoked by uid 22791); 6 Jun 2007 10:33:52 -0000 X-Spam-Check-By: sourceware.org Received: from anchor-post-33.mail.demon.net (HELO anchor-post-33.mail.demon.net) (194.217.242.91) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 06 Jun 2007 10:33:47 +0000 Received: from calivar.demon.co.uk ([83.104.54.243] helo=xl5.calivar.com) by anchor-post-33.mail.demon.net with esmtp (Exim 4.42) id 1Hvspe-0002dS-BE; Wed, 06 Jun 2007 10:33:39 +0000 Received: from xl5.calivar.com (localhost [127.0.0.1]) by xl5.calivar.com (Postfix) with ESMTP id BC5D313870D; Wed, 6 Jun 2007 11:33:37 +0100 (BST) To: =?utf-8?b?w5h5dmluZCBIYXJib2U=?= Cc: "eCos Discussion" References: From: Nick Garnett Original-Sender: nickg@ecoscentric.com Date: Wed, 06 Jun 2007 14:41:00 -0000 In-Reply-To: Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] Problems with ISR/DSR stacks X-SW-Source: 2007-06/txt/msg00067.txt.bz2 "=C3=98yvind Harboe" writes: > On 06 Jun 2007 10:31:37 +0100, Nick Garnett wrote: > > "=C3=98yvind Harboe" writes: > > > > > Enabling INFRA_DEBUG crashes my "rocket"... > > > > > > As far as I can tell the DSR runs run on the thread stack and not the > > > interrupt stack(from inside interrupt_end). > > > > No. DSRs run on the interrupt stack. This is what > > hal_interrupt_stack_call_pending_DSRs() does. >=20 > Ah. OK. I'll have to dig into that, but that does give interrupt > stacks a lot more oomph. The term "interrupt_stack" is a bit of a misnomer, it often gets used for all sorts of things: it's the startup stack; interrupts of course; running DSRs and sometimes exception handling. It depends on the HAL and who originally wrote it -- I recommend looking at the MIPS and PowerPC HALs for the best examples. >=20 > > If you disable the interrupt stack then you have to deal with the > > consequences. It is not recommended unless you know what you are > > doing. >=20 > I haven't added interrupt stacks to my HAL yet, but is sure is on my > list now(together with GDB support and a number of other things). :-) If you are doing a new port then the best thing to do at this stage is to just increase the minimum thread stack size by a couple of K, assuming you have the memory. That should allow you to get all the rest of the HAL running before dealing with the interrupt stack switching, which can be a bit tricky. --=20 Nick Garnett eCos Kernel Architect eCosCentric Limited http://www.eCosCentric.com/ The eCos experts Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571 Registered in England and Wales: Reg No 4422071. -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss