Next OSADL Events:
|
Breaking News:
2011-08-21 12:00
How to determine code coverage of a running program on the fly?A new HOWTO at the OSADL Website knows more
2011-06-12 12:00
Not yet registered at the Summer School in Linz, Austria?Do not miss talks by international experts on formal code analysis, Linux real-time and safety.
2011-05-19 12:00
Linux real-time news from San FranciscoThomas Gleixner at the Embedded Linux Conference 2011 |
Quick HOWTO
Download the file archive blocksys-0.2.tgz and type:
tar -zxvf blocksys-0.2.tgz
cd blocksys-0.2
make
modprobe blocksys
./mklatency
Check out the generated latency:
tail /var/log/messages
[..]
[..] kernel: blocksys: CPU #0 will be blocked for 2000000 nops
[..] kernel: blocksys: CPU #0 blocked about 1270 us
You may then wish to check and to calibrate latency analysis tools such as cyclictest or the OSADL Latency Measurement Box by executing mklatency while these tools are running. The CYCLES constant in the mklatency.c source file defines the duration of the latency.
File archive
Utility mklatency and blocksys driver | 3.7 K |
