During boot the driver scans physical memory (with MmMapIoSpace) to find
data a
preboot code has put there.
XP verifier blues
(0x000000c4 Call to MmMapIoSpace, but the caller has not locked down the
MDL pages)
at what I think is the border to yet “untouched” physical memory.
To use verifier, I was looking for another way to look at physical memory.
ZwMapViewOfSection works without errors for now, but I’m wondering about
the virtual address.
In the meantime I tried MmAllocateContiguousMemorySpecifyCache, which also
works.
Problem here is that the mapping often fails and slows down boot.
Regards
Else
“Nar Ganapathy[MS]”
ft.com> cc:
Sent by: Subject: [ntdev] Re: Driver Verifier and MmMapIoSpace replaced by
xxxxx@lis ZwMapViewOfSection
ts.osr.com
25.10.2002 18:44
Please respond to “NT
Developers Interest
List”
Can you provide an overview of what you are doing ? What is the error you
are getting from the driver verifier
–
Nar Ganapathy
Windows Core OS group
This posting is provided “AS IS” with no warranties, and confers no rights.
“Else Kluger” wrote in message news:xxxxx@ntdev…
>
> Hi all,
>
> good news for the weekend: I could finally solve the
> “Driver Verifier and MmMapIoSpace” problem with some support
> from Simon - thanks again.
>
> But I’m still not completely happy - I do not understand why the mapping
> with ZwMapViewOfSection returns a virtual address from user mode
> address space. As I’m calling from kernel mode, I exspected to receive
> a mapping in system space.
>
> No I do not need to access the mapping from a different process context,
> but I’m simply not sure if this will cause trouble again.
>
> Regards
> Else
>
>
>
>
>
—
You are currently subscribed to ntdev as: xxxxx@utimaco.de
To unsubscribe send a blank email to %%email.unsub%%