* [ECOS] instrumentation buffers
@ 2001-05-24 4:09 Marek Łącki
2001-05-24 5:45 ` Nick Garnett
0 siblings, 1 reply; 4+ messages in thread
From: Marek Łącki @ 2001-05-24 4:09 UTC (permalink / raw)
To: ecos-discuss
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,
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ECOS] instrumentation buffers
2001-05-24 4:09 [ECOS] instrumentation buffers Marek Łącki
@ 2001-05-24 5:45 ` Nick Garnett
0 siblings, 0 replies; 4+ messages in thread
From: Nick Garnett @ 2001-05-24 5:45 UTC (permalink / raw)
To: ecos-discuss
"=?iso-8859-2?B?TWFyZWsgo7Fja2k=?=" <lacki@rts.com.pl> writes:
> 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,
>
The times recorded in the instrumentation buffer are read out of the
hardware timer device with HAL_CLOCK_READ(). These values are not RTC
ticks, they are much higher resolution than that.
Since you are only instrumenting thread events, you are not seeing the
clock interrupts, where the hardware timer resets to zero. In the main
part of the program, each thread switch is driven by the clock
interrupt and occurs about 113 ticks later.
If you want to see what is really going on, enable the CLOCK and maybe
the INTR events too.
--
Nick Garnett, eCos Kernel Architect
Red Hat, Cambridge, UK
^ permalink raw reply [flat|nested] 4+ messages in thread
* [ECOS] instrumentation buffers
@ 2001-05-23 1:37 Marek Łącki
2001-05-23 8:41 ` Jonathan Larmour
0 siblings, 1 reply; 4+ messages in thread
From: Marek Łącki @ 2001-05-23 1:37 UTC (permalink / raw)
To: ecos-discuss
Hi
I have problem with a instrumentation buffers. I'm analyzing a thread's
events. I have a three threads (ID= 3,4,5).
Threads 3 and 4 have the same priority and thread 5 has lower priority. My
problem is with time, that is saved in table . Time , that is saved in the
first positions of table is greater than time in the last positions ( like
below) :
Record 05: type 0x0209, thread 3, time ffff9443,
Record 06: type 0x0207, thread 3, time ffffaca8,
Record 07: type 0x0202, thread 3, time ffffacb4,
Record 08: type 0x0201, thread 3, time ffffacf7,
Record 09: type 0x0209, thread 4, time ffffad11,
Record 10: type 0x0207, thread 4, time ffffc8b9,
Record 11: type 0x0202, thread 4, time ffffc8c4,
Record 12: type 0x0201, thread 4, time ffffc908,
Record 13: type 0x0209, thread 5, time ffffc922,
Record 14: type 0x0207, thread 5, time ffffc930,
Record 15: type 0x0202, thread 5, time ffffc93c,
Record 16: type 0x0201, thread 5, time ffffc97f
( any time jump )
Record 28: type 0x0207, thread 3, time 13a
Record 29: type 0x0202, thread 3, time 146
Record 30: type 0x0201, thread 3, time 189
Record 31: type 0x0207, thread 4, time 1ae
Record 32: type 0x0202, thread 4, time 1b9
Record 33: type 0x0201, thread 4, time 1fd
Record 34: type 0x0207, thread 5, time 221
Record 35: type 0x0202, thread 5, time 22d
Record 36: type 0x0201, thread 5, time 271
Record 44: type 0x0207, thread 3, time 13b......
What is wrong ????
MArek lacki@rts.com.pl
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ECOS] instrumentation buffers
2001-05-23 1:37 Marek Łącki
@ 2001-05-23 8:41 ` Jonathan Larmour
0 siblings, 0 replies; 4+ messages in thread
From: Jonathan Larmour @ 2001-05-23 8:41 UTC (permalink / raw)
To: Marek £±cki; +Cc: ecos-discuss
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
Marek £±cki wrote:
>
> Hi
> I have problem with a instrumentation buffers. I'm analyzing a thread's
> events. I have a three threads (ID= 3,4,5).
> Threads 3 and 4 have the same priority and thread 5 has lower priority. My
> problem is with time, that is saved in table . Time , that is saved in the
> first positions of table is greater than time in the last positions (
[snip]
Looking at kernel/VERSION/src/instrmnt/meminst.cxx I can't see how this
could happen because interrupts are disabled when the clock is read and
instrument record written. The thread priorities should be irrelevant. I
think you'll just have to debug it :-|.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2001-05-24 5:45 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-05-24 4:09 [ECOS] instrumentation buffers Marek Łącki
2001-05-24 5:45 ` Nick Garnett
-- strict thread matches above, loose matches on Subject: below --
2001-05-23 1:37 Marek Łącki
2001-05-23 8:41 ` Jonathan Larmour
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).