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
From the doc: “ZwMapViewOfSection maps a view of a section into the
virtual address space of a subject process.”
To me, that plainly reads that the returned address will be in user
space. On the other hand, I misunderstood myself a while back when I
tried to supply a desired address in kernel space. Of course I got an
error (something about a bad parameter).
So if you want a kernel-space address, try something else. Would
MmGetSystemAddressForMdlSafe work for you?
–
If replying by e-mail, please remove “nospam.” from the address.
James Antognini
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
>
>
>
>
>