public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@chez-thomas.org>
To: C B <csb_80@hotmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Performance timing
Date: Mon, 19 Nov 2007 14:36:00 -0000	[thread overview]
Message-ID: <47419EA7.4050400@chez-thomas.org> (raw)
In-Reply-To: <BAY105-W29BAAA81F6878EDC4D3FC2EA7E0@phx.gbl>

C B wrote:
> Thanks Mike.  That was very helpful.
>
> I guess my hope that I'd be able to make a simple call to get the time before and after my timed event was a little naive... :)
>
>
>   

This is certainly still possible.  It's pretty easy to extract the
pertinent code/functions
from tm_basic.  You just have to remember what you are actually
measuring - if
just knowing how long it takes to run a certain function is what you're
after, then
this will do fine.

One caveat: tm_basic's timing method falls apart if the function
requires more than
one system clock tick to accomplish.  If you suspect this to be the
case, you'll have
to capture the value of cyg_current_time() as well as HAL_CLOCK_READ().
>   
>> Date: Fri, 16 Nov 2007 13:55:28 -0600
>> From: arth2219@gmail.com
>> To: csb_80@hotmail.com
>> Subject: Re: [ECOS] Performance timing
>> CC: gary@mlbassoc.com; ecos-discuss@ecos.sourceware.org
>>
>> On Nov 16, 2007 1:47 PM, C B  wrote:
>>     
>>> System profiling is probably what I need.
>>>
>>> Unfortunately there isn't an implementation of the profiling timer for my target. Any information or guidance available that you're aware of for implementing this?
>>>       
>> The eCos Reference Manual has this functionality documented:
>> http://ecos.sourceware.org/docs-latest/ref/gprof.html
>>
>> It's pretty straight forward to implement with in your HAL. You'll
>> need a spare hardware timer to use for your instrumentation. Try
>> looking in other HALs that use the profile timer as an example.
>>
>> You need to setup two functions to implement the profile instrumentation:
>> 1.) int hal_enable_profile_timer(int resolution)
>> * Initializes hardware timer and ISR.
>> 2.) unsigned int profile_isr(CYG_ADDRWORD vector, CYG_ADDRWORD data,
>> HAL_SavedRegisters *regs)
>> * Saves current program counter
>> * Handles timer hardware
>>
>>     
-- 
Gary Thomas
Capt, CAP CO-021
home/office: (970) 352-4947,  cell: (970) 481-5112


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2007-11-19 14:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 18:54 [ECOS] networking support for my eCos application C B
2007-11-02 19:08 ` Gary Thomas
2007-11-05 16:12   ` C B
2007-11-05 18:43     ` Andrew Lunn
     [not found]       ` <BAY105-W2585C1EB05E16C54EA73C5EA890@phx.gbl>
2007-11-06  8:34         ` Andrew Lunn
2007-11-08 20:01   ` C B
2007-11-08 21:05     ` Andrew Lunn
2007-11-09  9:22     ` [ECOS] " John Dallaway
2007-11-09 13:32       ` [ECOS] " C B
2007-11-09 18:48         ` C B
2007-11-09 18:55           ` Andrew Lunn
2007-11-12 11:52             ` C B
2007-11-12 12:27               ` Gary Thomas
2007-11-12 18:11                 ` C B
2007-11-14 13:30                   ` [ECOS] Adding xscale support to my eCos config C B
2007-11-14 14:05                     ` Andrew Lunn
2007-11-14 14:13                       ` Mark Salter
2007-11-14 15:23                       ` C B
2007-11-14 15:24                         ` Gary Thomas
2007-11-14 20:11                           ` C B
2007-11-14 20:42                             ` C B
2007-11-16 18:15                               ` [ECOS] Performance timing C B
2007-11-16 19:47                                 ` Gary Thomas
2007-11-16 19:55                                   ` C B
2007-11-17  7:07                                     ` Mike Arthur
2007-11-19  5:19                                       ` C B
2007-11-19 14:36                                         ` Gary Thomas [this message]
2007-11-22 13:39                                           ` [ECOS] eCos compatible with arm-elf-gcc version 4.1.1? C B
2007-11-22 14:28                                             ` Lars Poeschel
2007-11-22 16:42                                               ` C B
2007-11-27 14:38                                               ` C B
2007-11-28 13:24                                                 ` C B
     [not found]             ` <BAY105-W28BEA5A1C91693C8BE5C8FEA870@phx.gbl>
2007-11-12 12:07               ` [ECOS] RE: networking support for my eCos application Andrew Lunn
2007-11-12 18:05                 ` C B

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47419EA7.4050400@chez-thomas.org \
    --to=gary@chez-thomas.org \
    --cc=csb_80@hotmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).