On Tue, Jun 29, 2010 at 5:33 PM, Andrew S. Baker <[email protected]> wrote: > Sort of... The drivers and such still need to be mapping into that space > (to a lesser degree than before) so that the 32-bit app can have access to > those services.
Right. The buffers which a 32-bit app uses to talk to the kernel/drivers need to be in the 32-bit app's virtual memory space. But they needed to be in the app's memory space before, too, so that's nothing new. But the driver code, hardware buffers, any driver internals, etc., shouldn't be exposed to the app. That's all kernel mode stuff, and should be 64-bit. Caveat #1: Emphasis "should". It wouldn't surprise me in the least to learn that some drivers were dragged kicking and screaming into the 64-bit world, and play games to keep everything under the 4 GiB line, because that's easier than fixing crappy code that assumes everything is 32 bits wide. Caveat #2: I'm not familiar with how usermode drivers on Windows work. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
