Private/bryan/iotargetopen waitloop

[ManOnTheMountainTech]

WdfIoTargetOpen Reliability Experiments

A thunk to pageable code is needed from IoRegisterPnPNotification in all options as WdfIoTargetOpen is pageable. The callback for RegisterPnPNotification runs at DPC.

Basic overview of code flow

1. The SelfManagedIoinit handler registers a PnP notification handler.
2. The PnP notification handler acts upon the arrival and departure of the IntelliMouse's interface No. 5.
3. For IntelliMouse taillight device interface arrival, a finite wait loop is started that calls WdfIoTargetOpen until it succeeds.
4. For IntelliMouse taillight device interface departure, if the WdfIoTargetOpen wait loop is executing, it is stopped.

This is option No. 3 of 3 options.

1. Just call WdfIoTargetOpen from a workitem.
2. Use a timer to set up a retry system. The timer creates a workitem that then calls WdfIoTargetOpen.
3. Use a wait loop inside a workitem. The workitem then calls WdfIoTargetOpen.

Tested for several days on one machine. There have been no failures of WdfIoTargetOpen.

This PR fixes issue #44.

[forderud]

Suggest that you slim down the PR to only perform the IoRegisterPlugPlayNotification stuff, so that we reduce the amount of code complexity required for fixing issue #44.

[ManOnTheMountainTech]

Do you want certmgr.exe, for installing certificates, to be checked in or have instructions for where to get it? From: Fredrik Orderud ***@***.***> Sent: Tuesday, February 20, 2024 10:35 AM To: forderud/IntelliMouseDriver ***@***.***> Cc: Bryan Allen Young ***@***.***>; Assign ***@***.***> Subject: Re: [forderud/IntelliMouseDriver] Private/bryan/iotargetopen waitloop (PR #51) Suggest that you slim down the PR to only perform the IoRegisterPlugPlayNotification stuff, so that we reduce the amount of code complexity required for fixing issue #44 <#44> . — Reply to this email directly, view it on GitHub <#51 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGBDV7262RLGW4KZDCEE7JTYUTUDZAVCNFSM6AAAAABDRPGEROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJUHAZTCNZYGA> . You are receiving this because you were assigned. <https://github.com/notifications/beacon/AGBDV77JNIRDTGEDKABBHRDYUTUDZA5CNFSM6AAAAABDRPGEROWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTUQRO2I.gif> Message ID: ***@***.***>

[forderud]

Do you want certmgr.exe, for installing certificates, to be checked in or have instructions for where to get it?

certmgr.exe is automatically in PATH if using a developer command prompt. It should therefore be sufficient to document usage of a "developer command prompt".