[ECOS] how to get thread realtime infomation

[ECOS] how to get thread realtime infomation

[xuas]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 4340 bytes --]

I found follow information in ecos-tutorial-ppc .
I want to know how can I get this information for trace and test.use codetest?
 
thanks

information:
80 Getting Started with eCos eCos
Appendix 1: Real-time
characterization
For a discussion of real-time performance measurement for eCos, see the eCos UsersÂ’
Guide.
Sample numbers:
Board: Cogent CMA MPC860 (PowerPC) Evaluation
Board
CPU : MPC860, revision A3 33MHz
eCOS Kernel Timings
Note: all times are in microseconds (.000001) unless otherwise stated
Reading the hardware clock takes 0 Â’ticksÂ’ overhead
... this value will be factored out of all other measurements
Clock interrupt took 14.46 microseconds (30 raw clock ticks)
Testing parameters:
Clock samples: 32
Threads: 24
Thread switches: 128
Mutexes: 32
Mailboxes: 32
Semaphores: 32
Scheduler operations: 128
Counters: 32
Alarms: 32
Confidence
Ave Min Max Var Ave Min Function
eCos Getting Started with eCos 83
27.58 25.60 44.16 2.07 93% 93% Create thread
5.94 5.76 7.04 0.22 93% 62% Yield thread [all suspended]
6.06 5.44 10.56 0.57 75% 75% Suspend [suspended] thread
5.42 4.80 9.60 0.53 87% 81% Resume thread
7.10 6.40 14.08 0.90 93% 87% Set priority
0.86 0.64 1.92 0.22 93% 50% Get priority
84 Getting Started with eCos eCos
16.74 15.04 36.48 2.47 93% 93% Kill [suspended] thread
6.14 5.76 10.56 0.55 93% 93% Yield [no other] thread
9.74 8.96 18.56 1.10 93% 93% Resume [suspended low prio] thread
5.28 4.80 9.28 0.54 93% 81% Resume [runnable low prio] thread
9.40 8.32 18.56 1.14 93% 93% Suspend [runnable] thread
6.04 5.76 8.96 0.38 93% 93% Yield [only low prio] thread
5.68 5.12 9.60 0.52 68% 75% Suspend [runnable->not runnable]
16.10 14.40 35.20 2.39 93% 93% Kill [runnable] thread
8.54 7.68 16.00 0.94 93% 87% Destroy [dead] thread
20.20 18.56 40.64 2.55 93% 93% Destroy [runnable] thread
39.02 36.48 57.28 3.28 87% 87% Resume [high priority] thread
13.13 12.80 22.08 0.15 78% 20% Thread switch
0.59 0.32 1.60 0.09 82% 16% Scheduler lock
3.67 3.52 5.12 0.17 99% 54% Scheduler unlock [0 threads]
3.67 3.52 4.80 0.17 99% 53% Scheduler unlock [1 suspended]
3.67 3.52 4.80 0.17 54% 54% Scheduler unlock [many suspended]
3.69 3.52 5.12 0.17 99% 50% Scheduler unlock [many low prio]
2.41 2.24 5.44 0.25 96% 75% Init mutex
6.83 6.40 11.84 0.34 75% 90% Lock [unlocked] mutex
6.74 6.40 13.12 0.40 96% 96% Unlock [locked] mutex
5.53 5.12 9.60 0.25 84% 12% Trylock [unlocked] mutex
4.84 4.48 7.36 0.17 78% 15% Trylock [locked] mutex
0.34 0.00 0.96 0.06 90% 3% Destroy mutex
56.10 55.68 59.52 0.21 93% 3% Unlock/Lock mutex
4.72 4.48 10.24 0.37 96% 96% Create mbox
0.75 0.64 1.92 0.16 75% 75% Peek [empty] mbox
6.79 6.40 12.80 0.41 96% 90% Put [first] mbox
0.46 0.32 1.60 0.19 93% 68% Peek [1 msg] mbox
6.68 6.40 12.16 0.37 96% 96% Put [second] mbox
0.50 0.32 1.60 0.20 93% 56% Peek [2 msgs] mbox


eCos Getting Started with eCos 85
7.13 6.40 14.08 0.49 90% 46% Get [first] mbox
6.97 6.40 13.44 0.47 84% 78% Get [second] mbox
6.24 5.76 11.52 0.38 78% 81% Tryput [first] mbox
5.98 5.44 11.20 0.39 78% 62% Peek item [non-empty] mbox
6.52 6.08 13.12 0.49 93% 81% Tryget [non-empty] mbox
5.50 5.12 10.24 0.30 68% 28% Peek item [empty] mbox
5.76 5.44 10.88 0.32 96% 96% Tryget [empty] mbox
0.50 0.32 1.60 0.19 96% 53% Waiting to get mbox
0.50 0.32 1.60 0.19 96% 53% Waiting to put mbox
7.45 7.04 15.04 0.49 96% 93% Delete mbox
37.47 36.80 48.64 0.70 96% 96% Put/Get mbox
2.49 2.24 6.08 0.28 96% 56% Init semaphore
5.09 4.80 8.64 0.27 46% 46% Post [0] semaphore
6.25 5.76 10.88 0.32 93% 3% Wait [1] semaphore
4.84 4.48 8.32 0.23 68% 25% Trywait [0] semaphore
4.98 4.80 8.00 0.26 96% 71% Trywait [1] semaphore
1.66 1.28 3.84 0.20 68% 15% Peek semaphore
1.24 0.96 3.20 0.17 65% 31% Destroy semaphore
40.74 40.32 49.28 0.53 96% 96% Post/Wait semaphore
2.65 2.24 6.08 0.23 84% 9% Create counter
0.85 0.64 2.24 0.22 90% 53% Get counter value
0.68 0.64 1.92 0.08 96% 96% Set counter value
7.13 6.72 8.64 0.24 78% 18% Tick counter
1.30 0.96 3.20 0.12 84% 12% Delete counter
3.69 3.52 7.68 0.29 96% 84% Create alarm
8.98 8.32 17.60 0.61 68% 62% Initialize alarm
0.96 0.64 2.88 0.14 71% 21% Disable alarm
8.76 8.32 17.60 0.59 96% 87% Enable alarm
1.99 1.60 5.12 0.21 81% 12% Delete alarm
7.44 7.36 9.92 0.15 96% 96% Tick counter [1 alarm]

Re: [ECOS] how to get thread realtime infomation

[Jonathan Larmour]

xuas wrote:
> 
> I found follow information in ecos-tutorial-ppc .
> I want to know how can I get this information for trace and test.use codetest?

Run the tm_basic test. You probably also want to enable
CYGVAR_KERNEL_COUNTERS_CLOCK_LATENCY in your eCos configuration.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

[ECOS] Re: Memory Layout on Assabet.

[Masashi Ichikawa]

Hello, 

I have a question about Assabet's Memory layout.

The "package\hal\arm\sa11x0\assabet\current\include\pkgcnf
\mlt_arm_sa11x0_assabet_rom.mlt"  file says:

version 0
region ram 0 2000000 0 !
region rom 50000000 40000 1 !
section fixed_vectors 0 1 0 1 1 0 1 0 20 20 !
section data 0 1 1 1 1 1 0 0 8000 bss !
section bss 0 4 0 1 0 1 0 1 heap1 heap1 !
section heap1 0 8 0 0 0 0 0 0 !
section rom_vectors 0 1 0 1 1 1 1 1 50000000 50000000 text text !
section text 0 4 0 1 0 1 0 1 fini fini !
section fini 0 4 0 1 0 1 0 1 rodata rodata !
section rodata 0 4 0 1 0 1 0 1 rodata1 rodata1 !
section rodata1 0 4 0 1 0 1 0 1 fixup fixup !
section fixup 0 4 0 1 0 1 0 1 gcc_except_table gcc_except_table !
section gcc_except_table 0 4 0 1 0 0 0 1 data !

This file says that ROM area starts from 0x50000000. But according
to the StrongARM's data sheet, 0x50000000 is a reserved area.
Is this correct? Any hints are welcome. Please help me.

best regards,
M.Ichikawa.

Re: [ECOS] Re: Memory Layout on Assabet.

[Jesper Skov]

>>>>> "Masashi" == Masashi Ichikawa <ichi@me.sony.co.jp> writes:

Masashi> Hello,

Masashi> I have a question about Assabet's Memory layout.
[snip]
Masashi> This file says that ROM area starts from 0x50000000. But
Masashi> according to the StrongARM's data sheet, 0x50000000 is a
Masashi> reserved area.  Is this correct? Any hints are
Masashi> welcome. Please help me.

eCos uses the MMU to move the areas around, allowing RAM to start at
0. See hal/arm/sa11x0/assabet/current/src/assabet_misc.

Jesper