[reactos] 04/04: [NTOS:MM] Use MiResolveDemandZeroFault instead of MiDispatchFault

[Timo Kreuzer]

https://git.reactos.org/?p=reactos.git;a=commitdiff;h=d17812f9331d8df208b6ab...

commit d17812f9331d8df208b6abd4e9f8628cffc60cc3
Author: Timo Kreuzer [e-mail]
AuthorDate: Wed Dec 27 15:20:52 2017 +0100

[NTOS:MM] Use MiResolveDemandZeroFault instead of MiDispatchFault
---
 ntoskrnl/mm/ARM3/pagfault.c | 16 +++++-----------
 1 file changed, 5 insertions(+), 11 deletions(-)

diff --git a/ntoskrnl/mm/ARM3/pagfault.c b/ntoskrnl/mm/ARM3/pagfault.c
index 69d70cc80b..3176a6b0d1 100644
--- a/ntoskrnl/mm/ARM3/pagfault.c
+++ b/ntoskrnl/mm/ARM3/pagfault.c
@@ -2121,18 +2121,12 @@ UserFault:
             return Status;
         }

-        /* Write a demand-zero PDE */
-        MI_WRITE_INVALID_PDE(PointerPde, DemandZeroPde);
-
-        /* Dispatch the fault */
-        Status = MiDispatchFault(TRUE,
-                                 PointerPte,
+        /* Resolve a demand zero fault */
+        MiResolveDemandZeroFault(PointerPte,
                                  PointerPde,
-                                 NULL,
-                                 FALSE,
-                                 PsGetCurrentProcess(),
-                                 TrapInformation,
-                                 NULL);
+                                 MM_READWRITE,
+                                 CurrentProcess,
+                                 MM_NOIRQL);
 #if MI_TRACE_PFNS
         UserPdeFault = FALSE;
 #endif