Fix POSIX port to respect configUSE_TIME_SLICING

[aggarg]

Description

Fix POSIX port to respect configUSE_TIME_SLICING.

Test Steps

int main( void )
{
    BaseType_t xTaskCreationResult = pdFAIL;

    xTaskCreationResult = xTaskCreate( prvTask1Function,
                                       "Task1",
                                       configMINIMAL_STACK_SIZE,
                                       NULL,
                                       tskIDLE_PRIORITY,
                                       NULL );
    configASSERT( xTaskCreationResult == pdPASS );

    vTaskStartScheduler();

    for( ;; )
    {

    }

    return 0;
}
/*-----------------------------------------------------------*/

static void prvTask1Function( void * pvParams )
{
    uint64_t i;
    BaseType_t xTaskCreationResult = pdFAIL;

    /* Silence warning about unused parameters. */
    ( void ) pvParams;

    xTaskCreationResult = xTaskCreate( prvTask2Function,
                                       "Task2",
                                       configMINIMAL_STACK_SIZE,
                                       NULL,
                                       tskIDLE_PRIORITY,
                                       NULL );
    configASSERT( xTaskCreationResult == pdPASS );

    for( ;; )
    {
        configPRINTF( "Task 1 running...\r\n" );

        for( i = 0; i < 100000000; i++ )
        {
            /* This loop is just a very crude delay implementation. */
        }
    }
}
/*-----------------------------------------------------------*/

static void prvTask2Function( void * pvParams )
{
    uint64_t i;

    /* Silence warning about unused parameters. */
    ( void ) pvParams;

    for( ;; )
    {
        configPRINTF( "Task 2 running...\r\n" );

        for( i = 0; i < 100000000; i++ )
        {
            /* This loop is just a very crude delay implementation. */
        }
    }
}
/*-----------------------------------------------------------*/

When configUSE_TIME_SLICING is set to 0, without this change, the above test outputs the following -

Task 1 running...
Task 2 running...
Task 1 running...
Task 2 running...

After the change, the above test outputs the following -

Task 1 running...
Task 1 running...
Task 1 running...
Task 1 running...

Checklist:

• I have tested my changes. No regression in existing tests.
• [NA] I have modified and/or added unit-tests to cover the code changes in this Pull Request.

Related Issue

NA.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[ActoryOu]

Is log in PR descrpition in wrong order? The scheduler would always pick Task 1 if configUSE_TIME_SLICING is set to 0, right?

PR description:

When configUSE_TIME_SLICING is set to 0, without this change, the above test outputs the following -

Task 1 running...
Task 2 running...
Task 1 running...
Task 2 running...

After the change, the above test outputs the following -

Task 1 running...
Task 1 running...
Task 1 running...
Task 1 running...

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud