From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <475EA9F4.3020306@domain.hid> Date: Tue, 11 Dec 2007 16:17:08 +0100 From: =?ISO-8859-1?Q?Ignacio_Garc=EDa_P=E9rez?= MIME-Version: 1.0 References: <475E76A0.4010007@domain.hid> <475E7CBA.7060300@domain.hid> <475E7F84.1040600@domain.hid> <475E8DAE.9070405@domain.hid> <2ff1a98a0712110541x12633fa3yb311214d9d0245a1@domain.hid> In-Reply-To: <2ff1a98a0712110541x12633fa3yb311214d9d0245a1@domain.hid> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] Application broken 2.3.4 ---> 2.4.0 List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: Jan Kiszka , xenomai@xenomai.org >> 2.3.x: returns -ETIMEDOUT but schedules the task for immediate execution. >> >> 2.4.0: returns -ETIMEDOUT and *does not* schedule the task for immediate >> execution. >> >> The more I think about it the mode I think this is a bug. >> >> I just can't think of a situation in which idate is in the past and it >> makes sense *not scheduling* the task for immediate execution... >> > > Why not passing TM_NOW as an initial date if you want the task to be > scheduled immediately instead of passing a date in the past ? It has > always worked and still works with Xenomai 2.4.0. > Let's suppose some event happens at time T0 which is recorded. Then, after some processing I'm reading to call rt_task_set_periodic, but a little delay has passed. If I use: rt_task_set_periodic(&mytask, TM_NOW, period) The periodic thread will be executed at: T0+D T0+D+period T0+D+period*2 T0+D+period*3 ... However, if I use rt_task_set_periodic(&mytask, recorded_time, period): T0+D T0+period T0+period*2 T0+period*3 That is, only the first execution is affected by the delay D. I think this option is clearly superior.