From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7173 invoked by alias); 31 Jul 2002 08:38:23 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 7166 invoked from network); 31 Jul 2002 08:38:22 -0000 Received: from unknown (HELO sccrmhc01.attbi.com) (204.127.202.61) by sources.redhat.com with SMTP; 31 Jul 2002 08:38:22 -0000 Received: from c1830598-a ([12.234.169.231]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP id <20020731083821.RCNR23732.sccrmhc01.attbi.com@c1830598-a>; Wed, 31 Jul 2002 08:38:21 +0000 Content-Type: text/plain; charset="iso-8859-1" From: NavEcos Reply-To: ecos@navosha.com To: Andrew Lunn Date: Wed, 31 Jul 2002 01:38:00 -0000 Cc: ecos-discuss@sources.redhat.com References: <02073022245703.00917@c1830598-a> <20020731080529.GD3392@biferten.ma.tech.ascom.ch> In-Reply-To: <20020731080529.GD3392@biferten.ma.tech.ascom.ch> MIME-Version: 1.0 Message-Id: <02073101425401.16908@c1830598-a> Content-Transfer-Encoding: 8bit Subject: Re: [ECOS] simple eCos profiler X-SW-Source: 2002-07/txt/msg00470.txt.bz2 On Wednesday 31 July 2002 01:05, Andrew Lunn wrote: > Hi Rich. > > This looks similar to the one i wrote a few years ago for eCos. Its > sitting in the ecos-discuss archive somewhere. That was for the > EBSA285, but could be easily ported to other targets. I find a > profiler useful at times, so it would be good to get something > incorporated. I just want to get something basic, perhaps later on a more polished tool can be made. > > I would like to get at least hooks for this into the main tree. It > > will not slow down eCos, it will be conditionally compilable. I > > can do the CDL if requested. How do I get it into CVS? > > Post the patch to ecos-patches. We the community can then take a look > at it and decide what needs doing to make it incorperatable, eg cdl, > making it more generic etc. There is a significant amount of code, most of it is not kernel code. Is it OK if I post a link to a webpage? I just have to set one up :D > > -Rich > > > > P.S. hal_ctrlc_check gets called a LOT and seems to get called > > more, the more pings I send it. I haven't debugged this to find out > > why, but it's perplexing. Anybody know what is going on with it? > > This function acts as the interface between the application network > stack and redboot. Each packet received by the application is passed > down to redboot to let it decide if the packet is actually for the > redboot stack, not the application stack. Oh. That name seem sort of obsfucated, but I get it. I will have to look at this more. I have found that it can take up significant time (like 33% of the active time) if I send enough network traffic through it. I have a question. When redboot "runs", can the application on top of redboot interrupt it? I haven't investigated the relationship between the two very much. > Andrew Thank you, -Rich -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss