diff options
| author | Nadav Amit <nadav.amit@gmail.com> | 2016-05-11 18:04:29 +0300 |
|---|---|---|
| committer | Radim Krčmář <rkrcmar@redhat.com> | 2016-06-02 18:38:50 +0300 |
| commit | b19ee2ff3b287fea48a2896a381e31319394fe58 (patch) | |
| tree | f1678e5632fa80ba384d77546a26fd2b6a963725 /tools/perf/scripts/python/sched-migration.py | |
| parent | 13e98fd1efc7f65cab1bba6cfab7859840f9aa66 (diff) | |
| download | linux-b19ee2ff3b287fea48a2896a381e31319394fe58.tar.xz | |
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 'tools/perf/scripts/python/sched-migration.py')
0 files changed, 0 insertions, 0 deletions
