Hi,
I'm not sure if this forum is appropriate, but I couldn't find anything else either.. Here goes.
When an application (say a win app) runs, it has its virtual address space, right? Now, how can a user mode application access the actual physical memory, like some "memory editors" seem to do? Also, can I/O-space be accessed by anything else than device drivers? Drivers apparently run in kernel mode, but do they have a virtual mem space? How can they then address the I/O-space?
Also, when a system call takes place from user mode code, where in mem does the code actually jump (in asm)?
I'm not sure if this forum is appropriate, but I couldn't find anything else either.. Here goes.
When an application (say a win app) runs, it has its virtual address space, right? Now, how can a user mode application access the actual physical memory, like some "memory editors" seem to do? Also, can I/O-space be accessed by anything else than device drivers? Drivers apparently run in kernel mode, but do they have a virtual mem space? How can they then address the I/O-space?
Also, when a system call takes place from user mode code, where in mem does the code actually jump (in asm)?