Doubt in testsuite design on smp schedulers

[Richi Dubey]

Also, heir means something that would be executing later, after the current
thread leaves cpu, right?

Why is it then that we are checking
<https://git.rtems.org/rtems/tree/testsuites/smptests/smpschededf02/init.c#n268>
against is_idle not against cpu->executing but for cpu->heir?

Please let me know.
Thanks

On Tue, Aug 4, 2020 at 3:18 PM Richi Dubey <richidubey at gmail.com> wrote:

> Hi,
>
> I wanted to learn about how the reset
> <https://git.rtems.org/rtems/tree/testsuites/smptests/smpschededf02/init.c#n219> function in
> the smpschededf02/init.c works/what it aims for.
>
> First
> <https://git.rtems.org/rtems/tree/testsuites/smptests/smpschededf02/init.c#n224>,
> we set the priority of the task in correspondence with their index, so Task
> 0 gets highest priority and set the affinity of all the task to both the
> processor.
>
> Then
> <https://git.rtems.org/rtems/tree/testsuites/smptests/smpschededf02/init.c#n229>,
> we suspend all the task by suspending their thread and enable the dispatch
> on thread's CPU.
>
> After that, why do we resume
> <https://git.rtems.org/rtems/tree/testsuites/smptests/smpschededf02/init.c#n234>
> the first two task and then again suspend
> <https://git.rtems.org/rtems/tree/testsuites/smptests/smpschededf02/init.c#n247>them
> by using the object id of their thread?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200804/2f086cad/attachment.html>