On Thu, May 15, 2008 at 3:50 PM, Matthieu <[EMAIL PROTECTED]> wrote: > > > On Thu, 15 May 2008 15:12:32 +0200, "Gilles Chanteperdrix" > <[EMAIL PROTECTED]> wrote: >> On Thu, May 15, 2008 at 11:28 AM, Gilles Chanteperdrix >> <[EMAIL PROTECTED]> wrote: >>> On Thu, May 15, 2008 at 8:10 AM, Matthieu >>> <[EMAIL PROTECTED]> wrote: >>> I think >>>> that VxWorks Task Control Block ,implemeted by WIND RIVER, is keeping >> the >>>> context in hard real-time. That's why I would like to know if there are >>>> other possibilities ? >>> >>> Yes, there are possibilities: fix your code not to use such internal >>> data as the WIND_TCB members. >> >> Even VxWorks documentation considers accessing WIND_TCB directly as a >> bad practice. See the doc of taskInfoGet at: >> >> > http://spacegrant.colorado.edu/~dixonc/vxworks/docs/vxworks/ref/taskShow.html >> >> So, what I would agree we can do is implement taskInfoGet. >> >> -- >> Gilles > > Well, what a great issue for me... > > But can I use other API implements of such kind of Tasks information, as > it's possible to mix APIs ? I think about Task Status or Thread State Flags > ?
The native task has rt_task_inquire. But rt_task_inquire, though it returns skin independent data, requires a native task pointer. So what you are missing is really taskInfoGet. -- Gilles _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
