Re: [Xenomai] rt_task_sleep_until() miss release point?

[ZIV-Alberto Ozalla Cantabrana <alberto.ozalla@cgglobal.com>]

Hi all,

Sorry about missing references to function cu_log().
You can omit cu_log calls (It is like printf).
There are in place to see where the log traces are taken.

Regards
Alberto
On 06/11/14 16:37, Gilles Chanteperdrix wrote:
> On Thu, Nov 06, 2014 at 03:24:08PM +0000, ZIV-Alberto Ozalla Cantabrana wrote:
>> Hi all,
>>
>> enclosed you will find two examples:
>>
>>    *   rt_task_sleep_until() missing release point, and
>>    *   rt_task_sleep_until() working fine.
>>
>> In the first example:
>>
>> Current time: t1=4205571 ms - Calculated next release point: t2= 4205572 ms
>> Real release: t3=4205574 ms
>>
>> Many Thanks
>> Alberto Ozalla
>>
>> Simplest example that shows the issue:
> When you post an example, please post a "self contained" one, i.e.
> one that can be compiled and run without:
> - any missing code or ellipses
> - references to functions not contained in the code or xenomai
> librairies, such as cu_log.
>
>> #1 SMP 20<6>kernel: [    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
> You do not need CONFIG_SMP on an uniprocessor, this adds some
> overhead. The overhead is mitigated on Xenomai 3, but not on xenomai
> 2.x.
>

-- 
Saludos,
Alberto Ozalla


CG DISCLAIMER: This email contains confidential information. It is intended exclusively for the addressees. If you are not an addressee, you must not store, transmit or disclose its contents. Instead please notify the sender immediately; and permanently delete this e-mail from your computer systems. We have taken reasonable precautions to ensure that no viruses are present. However, you must check this email and the attachments, for viruses. We accept no liability whatsoever, for any detriment caused by any transmitted virus.