diff options
| author | Hollis Blanchard | 2008-11-10 21:57:36 +0100 |
|---|---|---|
| committer | Avi Kivity | 2008-12-31 15:52:26 +0100 |
| commit | fe4e771d5c37f0949047faf95d16a512b21406bf (patch) | |
| tree | 518b4ff17a8e1e62b747ce1912c08b62883d2855 /arch/x86/kvm/vmx.h | |
| parent | KVM: ppc: use prefetchable mappings for guest memory (diff) | |
| download | kernel-qcow2-linux-fe4e771d5c37f0949047faf95d16a512b21406bf.tar.gz kernel-qcow2-linux-fe4e771d5c37f0949047faf95d16a512b21406bf.tar.xz kernel-qcow2-linux-fe4e771d5c37f0949047faf95d16a512b21406bf.zip | |
KVM: ppc: fix userspace mapping invalidation on context switch
We used to defer invalidating userspace TLB entries until jumping out of the
kernel. This was causing MMU weirdness most easily triggered by using a pipe in
the guest, e.g. "dmesg | tail". I believe the problem was that after the guest
kernel changed the PID (part of context switch), the old process's mappings
were still present, and so copy_to_user() on the "return to new process" path
ended up using stale mappings.
Testing with large pages (64K) exposed the problem, probably because with 4K
pages, pressure on the TLB faulted all process A's mappings out before the
guest kernel could insert any for process B.
Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'arch/x86/kvm/vmx.h')
0 files changed, 0 insertions, 0 deletions