From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: Using instrument buffer by applications?
Date: Mon, 21 Jul 2008 19:28:00 -0000 [thread overview]
Message-ID: <g62nvo$fo9$1@ger.gmane.org> (raw)
In-Reply-To: <20080721190838.GX4167@lunn.ch>
On 2008-07-21, Andrew Lunn <andrew@lunn.ch> wrote:
>> Has anybody used the instrument buffer scheme to log
>> application events?
>
> I have, but my events were over a short period of time.
For my apps, there are going to be bursts of a few events
separated by gaps that are pretty large (on the scale of the
HAL counter).
> Interestingly, if you look in
> packages/kernel/current/src/instrmnt/meminst.cxx you will
> find:
>
> #ifdef CYGVAR_KERNEL_COUNTERS_CLOCK
> // p->timestamp = Cyg_Clock::real_time_clock->current_value_lo();
> HAL_CLOCK_READ( &p->timestamp );
> #else
> p->timestamp = 0;
> #endif
>
> so it looks like you can change from HW ticks to slower eCos
> timer ticks.
I saw that, but assumed it would break other stuff if I changed
it. I thought about adding aonther field so that it recorded
both the low 32 bits of the system tick counter and the value
from HAL_CLOCK_READ(). That would get me a rollover at about 3
(1ms) or 30 years (10ms), but I'd still have a resolution of
about 25ns.
years with
--
Grant Edwards grante Yow! Hello... IRON
at CURTAIN? Send over a
visi.com SAUSAGE PIZZA! World War
III? No thanks!
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2008-07-21 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 19:01 [ECOS] " Grant Edwards
2008-07-21 19:09 ` Andrew Lunn
2008-07-21 19:28 ` Grant Edwards [this message]
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='g62nvo$fo9$1@ger.gmane.org' \
--to=grante@visi.com \
--cc=ecos-discuss@sources.redhat.com \
/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).