From: Andrew Lunn <andrew@lunn.ch>
To: Pieter-Jan Busschaert <pieterjan.busschaert@gmail.com>
Cc: "Alois Z." <alois@gmx.at>, ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Thread activation disturbed by lower priority threads]
Date: Fri, 17 Aug 2007 08:14:00 -0000 [thread overview]
Message-ID: <20070817081405.GF17702@lunn.ch> (raw)
In-Reply-To: <950a36fb0708170108s3d66dde6yc42e5bd49efaff36@mail.gmail.com>
> This last option creates a binary ( [ecos.ecc
> path]/install/bin/dump_instr ) which can be used to examine the
> instrumentation buffer. I had to modify the source a little bit to
> account for little endian / big endian differences, support for
> wrapped around buffers and continuous time (ie: no time reset after
> each clock IRQ). Attached is my source file (
> ecos\packages\kernel\host\instr\dump_instr.c )
Could you produce a clean patch which i can commit to CVS?
Thanks
Andrew
--
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 prev parent reply other threads:[~2007-08-17 8:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 7:34 Alois Z.
2007-08-17 8:08 ` Pieter-Jan Busschaert
2007-08-17 8:14 ` Andrew Lunn [this message]
2007-08-17 8:46 ` Pieter-Jan Busschaert
2007-08-17 8:59 ` Andrew Lunn
2007-08-23 20:38 ` Alois Zoitl
-- strict thread matches above, loose matches on Subject: below --
2007-08-07 14:02 Alois Z.
2007-08-07 14:41 ` Andrew Lunn
2007-08-07 17:35 ` Paul D. DeRocco
2007-08-07 18:55 ` Andrew Lunn
[not found] ` <20070808075810.250840@gmx.net>
2007-08-08 8:10 ` Andrew Lunn
2007-08-16 20:05 ` Alois Zoitl
2007-08-16 20:22 ` Andrew Lunn
[not found] ` <20070817072849.22110@gmx.net>
2007-08-17 8:08 ` Andrew Lunn
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=20070817081405.GF17702@lunn.ch \
--to=andrew@lunn.ch \
--cc=alois@gmx.at \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=pieterjan.busschaert@gmail.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).