49dd2c4928
When we use TID=N userspace mappings, we must ensure that kernel mappings have been destroyed when entering userspace. Using TID=1/TID=0 for kernel/user mappings and running userspace with PID=0 means that userspace can't access the kernel mappings, but the kernel can directly access userspace. The net is that we don't need to flush the TLB on privilege switches, but we do on guest context switches (which are far more infrequent). Guest boot time performance improvement: about 30%. Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com> Signed-off-by: Avi Kivity <avi@qumranet.com> |
||
|---|---|---|
| .. | ||
| 44x_tlb.c | ||
| 44x_tlb.h | ||
| booke_guest.c | ||
| booke_host.c | ||
| booke_interrupts.S | ||
| emulate.c | ||
| Kconfig | ||
| Makefile | ||
| powerpc.c | ||