Re: Tracing task id.

2015-03-26 Thread Chris Johns
On 27/03/2015 12:47 am, Joel Sherrill wrote: > On 03/26/2015 08:41 AM, Gedare Bloom wrote: >> There are unused fields in the (32-bit) Objects_Id, but none are >> "reserved". Currently only 2-bits of the API are used, although 4 bits >> are available. Also, if you're not using RTEMS_MULTIPROCESSING,

Re: Tracing task id.

2015-03-26 Thread Joel Sherrill
On 03/26/2015 08:41 AM, Gedare Bloom wrote: There are unused fields in the (32-bit) Objects_Id, but none are "reserved". Currently only 2-bits of the API are used, although 4 bits are available. Also, if you're not using RTEMS_MULTIPROCESSING, I guess none of the node bits are used. Look at _Ob

Re: Tracing task id.

2015-03-26 Thread Gedare Bloom
There are unused fields in the (32-bit) Objects_Id, but none are "reserved". Currently only 2-bits of the API are used, although 4 bits are available. Also, if you're not using RTEMS_MULTIPROCESSING, I guess none of the node bits are used. Gedare On Wed, Mar 25, 2015 at 10:52 PM, Chris Johns wro

Tracing task id.

2015-03-25 Thread Chris Johns
Hi, Is there are bit in the Id that could be reserved and used to record the interrupt nesting state when tracing ? This saves having to find a bit somewhere else in record to capture this piece of information. I am thinking about testing the irq nesting level and if set recording this. Chris __