summaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorHollis Blanchard <hollisb@us.ibm.com>2008-11-10 21:57:35 +0100
committerAvi Kivity <avi@redhat.com>2008-12-31 15:52:26 +0100
commitdf9b856c454e331bc394c80903fcdea19cae2a33 (patch)
treeaa266ad64c3bed1f895d2f8132b62c25bae882e4 /net
parentKVM: ppc: use MMUCR accessor to obtain TID (diff)
downloadlinux-df9b856c454e331bc394c80903fcdea19cae2a33.tar.xz
linux-df9b856c454e331bc394c80903fcdea19cae2a33.zip
KVM: ppc: use prefetchable mappings for guest memory
Bare metal Linux on 440 can "overmap" RAM in the kernel linear map, so that it can use large (256MB) mappings even if memory isn't a multiple of 256MB. To prevent the hardware prefetcher from loading from an invalid physical address through that mapping, it's marked Guarded. However, KVM must ensure that all guest mappings are backed by real physical RAM (since a deliberate access through a guarded mapping could still cause a machine check). Accordingly, we don't need to make our mappings guarded, so let's allow prefetching as the designers intended. Curiously this patch didn't affect performance at all on the quick test I tried, but it's clearly the right thing to do anyways and may improve other workloads. Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com> Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions