From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Using instrument buffer by applications?
Date: Mon, 21 Jul 2008 19:01:00 -0000 [thread overview]
Message-ID: <g62md3$bb8$1@ger.gmane.org> (raw)
I'm looking into ways to get some sort of event history/log
info out of eCos apps. I've been looking at the instrument
buffer mechanism that's implimented in the eCos kernel, but it
doesn't really look appropriate.
The main issue is that the timestamp in a log record is the
number of HAL counter ticks since the last system tick. The
only way that value is meaningful is if you have the kernel
configured to instrument system ticks. But, if you do that the
instrument buffer fills up with virtually nothing but 1ms
system ticks. Even with 10ms system ticks, they're still going
to completely swamp out events that might only happen once
every few minutes.
Has anybody used the instrument buffer scheme to log
application events?
--
Grant Edwards grante Yow! CHUBBY CHECKER just
at had a CHICKEN SANDWICH in
visi.com downtown DULUTH!
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2008-07-21 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 19:01 Grant Edwards [this message]
2008-07-21 19:09 ` Andrew Lunn
2008-07-21 19:28 ` [ECOS] " Grant Edwards
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='g62md3$bb8$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).