Unexpected behaviour of ScheduledTask module about dmf

[samtertzakian]

The pending PR has a fix for this issue: #178

[samtertzakian]

Resolved by Release v1.1.98. Please use new DMF_ScheduledTask_ExecuteNowDeferredEx() Method. It honors the return value correctly.

[samtertzakian]

Sorry for delayed response.

See resolution below...

[samtertzakian]

Ok, I see what the issue is:

You need to use:

dmfSchedulerCfg.ExecuteWhen = ScheduledTask_ExecuteWhen_PrepareHardware;
or
dmfSchedulerCfg.ExecuteWhen = ScheduledTask_ExecuteWhen_D0Entry;

When you do so you do not use:

DMF_ScheduledTask_ExecuteNowDeferred() or DMF_ScheduledTask_ExecuteNow()
Instead the scheduled task will be automatically started when PrepareHardware or D0Entry happen.

In this case, the scheduled task callback will be called automatically and repeatedly as you expected.

You used:

dmfSchedulerCfg.ExecuteWhen = ScheduledTask_ExecuteWhen_Other;

In this case you also used: DMF_ScheduledTask_ExecuteNowDeferred() or DMF_ScheduledTask_ExecuteNow()

But when you do so using the Method, the automatic retry does not happen (by design).

This is not intuitive and can be considered to be a bug.
At the minimum, the documentation and comments in the code will be updated to reflect this behavior.
But, if possible, we will see if we can update the code so that "Other" mode allows periodic call of Scheduled Task so that it works as one would expect.

Thank you for your feedback.

Please contact [email protected] for faster responses.

[nefarius]

Thank you very much for the insights, I will test with ScheduledTask_ExecuteWhen_D0Entry then, should be alright.

Appreciate the addition to documentation!

One more question though; am I then by design allowed to still call DMF_ScheduledTask_ExecuteNowDeferred() "in between" when I need to not await the specified timeout value? I'd like to utilize it that way to send a packet to my device ASAP when necessary and sticking to just using the scheduler callback would allow me to not care about synchronization as the only sending code would remain in that callback.

Cheers!

[samtertzakian]

Yes, you instantiate using ScheduledTask_ExecuteWhen_D0Entry. Then, you can use DMF_ScheduledTask_ExecuteNow() to cause the same callback to be immediately called. In this case, however, you may need to acquire and release a lock in the callback to make sure that the deferred callback using timer does not race with your immediate execution. In fact, there is a comment in the code that explains that. If I recall, we specifically added DMF_ScheduledTask_ExecuteNow() for the exact purpose you describe.

Having said all that, I will update the documentation to explain all this (and possibly add a Method to do what you originally intended). I will keep this issue open until the documentation is updated. Let me know if you have any other questions. Thank you for the feedback.

[nefarius]

Yes, you instantiate using ScheduledTask_ExecuteWhen_D0Entry. Then, you can use DMF_ScheduledTask_ExecuteNow() to cause the same callback to be immediately called. In this case, however, you may need to acquire and release a lock in the callback to make sure that the deferred callback using timer does not race with your immediate execution. In fact, there is a comment in the code that explains that. If I recall, we specifically added DMF_ScheduledTask_ExecuteNow() for the exact purpose you describe.

It works now exactly as I need it with these adjustments, thanks! Also introduced a lock just to be safe.