public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Marek &Lstrok;&aogon;cki" <lacki@rts.com.pl>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] instrumentation buffers
Date: Thu, 24 May 2001 04:09:00 -0000	[thread overview]
Message-ID: <004001c0e43e$f5b18110$1400a8c0@rts.com.pl> (raw)

Hi
I have a  gquestion. Does  threads events are wrote in order of time??????.
Is counter reset during of working ???
I have unexpected values in time positions. I tested a timeslicing. I have
three threads( ID =3,4,5)  with the same priority= 10. I received results
 switching between thread ID-3 ,4 ,5 is sometime in the same time - and
settings of timeslicing are  5 ticks):
How can  I solve this problem ????

Record 00: type 0x0205, thread 1, time   778,
Record 01: type 0x0205, thread 1, time   806,
Record 02: type 0x0205, thread 1, time   835,
Record 03: type 0x0209, thread 2, time -27810,
Record 04: type 0x0201, thread 2, time -27612,
Record 05: type 0x0209, thread 3, time -27587,
Record 06: type 0x0201, thread 3, time   113,
Record 07: type 0x0209, thread 4, time   139,
Record 08: type 0x0201, thread 4, time   113,
Record 09: type 0x0209, thread 5, time   139,
Record 10: type 0x0201, thread 5, time   112,
Record 11: type 0x0201, thread 3, time   113,
Record 12: type 0x0201, thread 4, time   112,
Record 13: type 0x0201, thread 5, time   113,
Record 14: type 0x0201, thread 3, time   113,
Record 15: type 0x0201, thread 4, time   112,
Record 16: type 0x0201, thread 5, time   112,
Record 17: type 0x0201, thread 3, time   112,
Record 18: type 0x0201, thread 4, time   112,
Record 19: type 0x0201, thread 5, time   114,
Record 20: type 0x0201, thread 3, time   113,
Record 21: type 0x0201, thread 4, time   112,
Record 22: type 0x0201, thread 5, time   113,
Record 23: type 0x0201, thread 3, time   112,
Record 24: type 0x0201, thread 4, time   113,
Record 25: type 0x0201, thread 5, time   113,
Record 26: type 0x0201, thread 3, time   113,
Record 27: type 0x0201, thread 4, time   112,
Record 28: type 0x0201, thread 5, time   113,
Record 29: type 0x0201, thread 3, time   113,
Record 30: type 0x0201, thread 4, time  5061,
Record 31: type 0x0000, thread 0, time     0,

             reply	other threads:[~2001-05-24  4:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-24  4:09 Marek &Lstrok;&aogon;cki [this message]
2001-05-24  5:45 ` Nick Garnett
  -- strict thread matches above, loose matches on Subject: below --
2001-05-23  1:37 Marek &Lstrok;&aogon;cki
2001-05-23  8:41 ` Jonathan Larmour

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='004001c0e43e$f5b18110$1400a8c0@rts.com.pl' \
    --to=lacki@rts.com.pl \
    --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).