summaryrefslogtreecommitdiffstats
path: root/arch/x86/lib/csum-partial_64.c
diff options
context:
space:
mode:
authorNadav Amit2016-05-11 17:04:29 +0200
committerRadim Krčmář2016-06-02 17:38:50 +0200
commitb19ee2ff3b287fea48a2896a381e31319394fe58 (patch)
treef1678e5632fa80ba384d77546a26fd2b6a963725 /arch/x86/lib/csum-partial_64.c
parentMerge tag 'kvm-arm-for-v4.7-rc2' of git://git.kernel.org/pub/scm/linux/kernel... (diff)
downloadkernel-qcow2-linux-b19ee2ff3b287fea48a2896a381e31319394fe58.tar.gz
kernel-qcow2-linux-b19ee2ff3b287fea48a2896a381e31319394fe58.tar.xz
kernel-qcow2-linux-b19ee2ff3b287fea48a2896a381e31319394fe58.zip
KVM: x86: avoid write-tearing of TDP
In theory, nothing prevents the compiler from write-tearing PTEs, or split PTE writes. These partially-modified PTEs can be fetched by other cores and cause mayhem. I have not really encountered such case in real-life, but it does seem possible. For example, the compiler may try to do something creative for kvm_set_pte_rmapp() and perform multiple writes to the PTE. Signed-off-by: Nadav Amit <nadav.amit@gmail.com> Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
Diffstat (limited to 'arch/x86/lib/csum-partial_64.c')
0 files changed, 0 insertions, 0 deletions