Diagnostics_TASK_SWITCHED_OUT

Kernel
1

meandmyself wrote on Wednesday, March 25, 2009:

strangely enough the first macro to be called is:

traceTASK_SWITCHED_OUT
not
traceTASK_SWITCHED_IN

I saw the code of
void vTaskSwitchContext( void ) in tasks.c and in fact the _OUT macro is called at the begin and the _IN at the end.

Any reason for this?
Shouldn’t at least a call  to the _IN macro be missing when the task is put to run for the very first time?

thanks

2

rtel wrote on Wednesday, March 25, 2009:

traceTASK_SWITCHED_OUT() should be called first.  When SWICTHED_OUT is called pxCurrentTCB points to the TCB of the task that was running prior to the context switch.  When SWITCHED_IN is called pxCurrentTCB points to the TCB of the task that is selected to run when next.

Regards.

3

liljenvall wrote on Tuesday, September 11, 2012:

Hi,

But the very first task will not be preceeded by an SWITCHED_IN call, I think it would be good to get an call also before the first task is started, this way i can measure the execution time of the first run for the first task aswell.

Best Regards
Fredrik Liljenvall

4

rtel wrote on Tuesday, September 11, 2012:

The scheduler is started from the port layer - that is - the code that is not common to every microcontroller.  It would not be easy to go through all 31 ports and update the code to make a call to the SWITCHED_IN macro.

You know which task is running first, because the SWITCHED_OUT macro that gets called first will tell you.  The only information you are missing is the exact time the first task executed for.  It would be easier to get this by adding in a new macro in vTaskStartScheduler().  The new macro could then be used to start the run time stats counter - if it was already running before the scheduler started.  Please add a feature request in the SourceForge feature request tracker if you would like that added.

Regards.

5

liljenvall wrote on Thursday, September 13, 2012:

Hi Richard,

Thanks for the reply,

I was thinking that adding a traceTASK_SWITCHED_IN(); macro just before xPortStartScheduler() is called inside the generic vTaskStartScheduler code.

Works good when i test it,

I will add an feature request for it or i can send an patch if you want?

Best Regards Fredrik