[Xenomai-core] Problem running klatency test

[Xenomai-core] Problem running klatency test

[Shashank Bhatia]

Dear All,

          I could manage to compile my patched kernel on ubuntu using
the following guide : https://wiki.ubuntu.com/KernelTeam/GitKernelBuild

Now when i installed Xenomai, i could run the latency tests, but when i
tried to run the kernel space latency test, i found the following error.


root@domain.hid# ./run 
*
*
* Type ^C to stop this application.
*
*
open(/proc/xenomai/registry/native/pipes/klat_pipe): No such file or
directory
modprobe klat_mod or try the -P option?



Please help to get this running.


The dmesg | grep Xenomai gave the following output:
[    4.353912] I-pipe: Domain Xenomai registered.
[    4.353949] Xenomai: hal/i386 started.
[    4.354530] Xenomai: real-time nucleus v2.4.8 (Lords Of Karma)
loaded.
[    4.354612] Xenomai: SMI-enabled chipset found
[    4.354623] Xenomai: SMI workaround enabled
[    4.354647] Xenomai: starting native API services.
[    4.354650] Xenomai: starting POSIX services.
[    4.354693] Xenomai: starting RTDM services.



Thanks in advance


-------------------------------------
Hi-Tech Gears Limited, Gurgaon, India

Re: [Xenomai-core] Problem running klatency test

[Stefan Kisdaroczi]

[-- Attachment #1: Type: text/plain, Size: 1796 bytes --]

Hi,

Shashank Bhatia schrieb:
> Dear All,
> 
>           I could manage to compile my patched kernel on ubuntu using
> the following guide : https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
> 
> Now when i installed Xenomai, i could run the latency tests, but when i
> tried to run the kernel space latency test, i found the following error.
> 
> 
> root@domain.hid# ./run 
> *
> *
> * Type ^C to stop this application.
> *
> *
> open(/proc/xenomai/registry/native/pipes/klat_pipe): No such file or
> directory
> modprobe klat_mod or try the -P option?

1) go to your xeno-patched kernel tree
2) make menuconfig
3) navigate to Real-time sub-system ---> Drivers ---> Testing Drivers
4) enable 'Timer benchmark driver'
5) a new options pops up: 'Kernel-only latency measurement module'
6) enable this option
7) rebuild kernel & install kernel & reboot
8) try again, if you enabled it as a module (M) and not built-in (*)
   use modprobe to load to module

kisda

> The dmesg | grep Xenomai gave the following output:
> [    4.353912] I-pipe: Domain Xenomai registered.
> [    4.353949] Xenomai: hal/i386 started.
> [    4.354530] Xenomai: real-time nucleus v2.4.8 (Lords Of Karma)
> loaded.
> [    4.354612] Xenomai: SMI-enabled chipset found
> [    4.354623] Xenomai: SMI workaround enabled
> [    4.354647] Xenomai: starting native API services.
> [    4.354650] Xenomai: starting POSIX services.
> [    4.354693] Xenomai: starting RTDM services.
> 
> 
> 
> Thanks in advance
> 
> 
> -------------------------------------
> Hi-Tech Gears Limited, Gurgaon, India
> 
> 
> 
> 
> 
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-core] Problem running klatency test

[Stefan Kisdaroczi]

[-- Attachment #1.1: Type: text/plain, Size: 217 bytes --]

Shashank Bhatia schrieb:
> [...]
> open(/proc/xenomai/registry/native/pipes/klat_pipe): No such file or
> directory
> modprobe klat_mod or try the -P option?

the module ist called xeno_klat. patch attached.


[-- Attachment #1.2: xeno_klat.patch --]
[-- Type: text/plain, Size: 513 bytes --]

diff --git a/src/testsuite/klatency/klatency.c b/src/testsuite/klatency/klatency.c
index a22cd59..c419402 100644
--- a/src/testsuite/klatency/klatency.c
+++ b/src/testsuite/klatency/klatency.c
@@ -187,7 +187,7 @@ int main(int argc, char **argv)
 		if (benchdev == -1) {
 			perror("open(/proc/xenomai/registry/native/pipes/klat_pipe)");
 			fprintf(stderr,
-				"modprobe klat_mod or try the -P option?\n");
+				"modprobe xeno_klat or try the -P option?\n");
 			exit(EXIT_FAILURE);
 		}
 	} else {

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]