diff options
| author | Nadav Amit <[email protected]> | 2016-05-11 15:04:29 +0000 |
|---|---|---|
| committer | Radim Krčmář <[email protected]> | 2016-06-02 15:38:50 +0000 |
| commit | b19ee2ff3b287fea48a2896a381e31319394fe58 (patch) | |
| tree | f1678e5632fa80ba384d77546a26fd2b6a963725 /scripts/gdb/vmlinux-gdb.py | |
| parent | Merge tag 'kvm-arm-for-v4.7-rc2' of git://git.kernel.org/pub/scm/linux/kernel... (diff) | |
| download | kernel-b19ee2ff3b287fea48a2896a381e31319394fe58.tar.gz kernel-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 <[email protected]>
Signed-off-by: Radim Krčmář <[email protected]>
Diffstat (limited to 'scripts/gdb/vmlinux-gdb.py')
0 files changed, 0 insertions, 0 deletions
