From mboxrd@z Thu Jan 1 00:00:00 1970 References: <55DF2471.6030006@cern.ch> <55DF2868.2070804@xenomai.org> <55DF32E3.1010706@cern.ch> <55E015FE.7000302@xenomai.org> <55E0560B.4040601@gmail.com> <55E05817.90601@xenomai.org> From: Konstantinos Chalas Message-ID: <55E0594C.2060704@gmail.com> Date: Fri, 28 Aug 2015 14:51:24 +0200 MIME-Version: 1.0 In-Reply-To: <55E05817.90601@xenomai.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] Cyclictest in Xenomai-3 List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Philippe Gerum , xenomai@xenomai.org Hello, root@beaglebone:~# uname -a Linux beaglebone 3.14.44+ #1 SMP PREEMPT Wed Aug 26 23:41:20 CEST 2015 armv7l GNU/Linux and ipipe-core-3.14.44-arm-12 Thanks On 08/28/2015 02:46 PM, Philippe Gerum wrote: > On 08/28/2015 02:37 PM, Konstantinos Chalas wrote: >> Great! Now, it is much better! Thanks for the interest. >> >> I have noticed something else, when using clock_nanosleep, there is >> something wrong going on. Example output with clock_nanosleep: >> >> root@beaglebone:~# cyclictest -p 99 -i 250 -n >> # /dev/cpu_dma_latency set to 0us >> policy: fifo: loadavg: 1.13 1.18 1.15 1/243 2385 >> >> T: 0 ( 2384) P:99 I:250 C: 122168 Min: 0 Act: 9 *Avg:2147483647* >> Max: -1 >> >> The Avg value jumps to this insane number. >> I didn't find any differences between the vanilla cyclictest and the >> xenomai-2.6 upstream cyclictest regarding the use of clock_nanosleep. >> Any ideas of where this behaviour would come from? > Which kernel and I-pipe release are you running? >