No, the "kernel" part of the address space is not accessable in user space.
It is just the physical memory mapped into the address space as a big chunk.
The purpose is that user-space/kernel space switches (e.g. due to system calls
do not require a rather expensive (TLB flush) address space switch.
-Michi
so does it mean in theory at least, you _don't have to_ map the kernel
code into the 4GB process address space? It is just that when you do
want kernel to run something on your behalf (through syscall), it is
more expensive to do the mapping? or is it just plain not possible?
ruby
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
