You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear sir:
I saw you in the graphics-driver-samples issue, and then saw that you work at Microsoft, so I want to ask you a question about wddm, thank you very much, the question is as follows:
I want to know how the wddm interrupt is registered. In this sample, I don't see the place where the interrupt is registered. I only see the enable and disable interrupt, and the interrupt processing. I guess whether the wddm interrupt is done for us by windows dxgkrnl , the process I guess is to add the interrupt information to the dsdt table in uefi, after windows dxgkrnl obtains the dsdt table, it registers the interrupt by itself, and registers the DxgkDdiInterruptRoutine function as a callback function, and the mini port driver is only responsible for enable and close and process interrupt, Not sure if my assumption is right, can you tell me the answer?
The text was updated successfully, but these errors were encountered:
Dear sir:
I saw you in the graphics-driver-samples issue, and then saw that you work at Microsoft, so I want to ask you a question about wddm, thank you very much, the question is as follows:
I want to know how the wddm interrupt is registered. In this sample, I don't see the place where the interrupt is registered. I only see the enable and disable interrupt, and the interrupt processing. I guess whether the wddm interrupt is done for us by windows dxgkrnl , the process I guess is to add the interrupt information to the dsdt table in uefi, after windows dxgkrnl obtains the dsdt table, it registers the interrupt by itself, and registers the DxgkDdiInterruptRoutine function as a callback function, and the mini port driver is only responsible for enable and close and process interrupt, Not sure if my assumption is right, can you tell me the answer?
The text was updated successfully, but these errors were encountered: