diff options
author | Yan Zhao <[email protected]> | 2024-03-08 17:09:28 -0800 |
---|---|---|
committer | Sean Christopherson <[email protected]> | 2024-06-07 07:18:02 -0700 |
commit | 65a4de0ffd975af7e2ffc9acb875b6a8ae7ee1aa (patch) | |
tree | fe310365b89d2cc9d4464e40aaad9e12c86c59c1 /lib/test_fortify/write_overflow-strncpy-src.c | |
parent | f05eda16037f9363297561bd28f318a6d7833d35 (diff) |
KVM: x86: Ensure a full memory barrier is emitted in the VM-Exit path
Ensure a full memory barrier is emitted in the VM-Exit path, as a full
barrier is required on Intel CPUs to evict WC buffers. This will allow
unconditionally honoring guest PAT on Intel CPUs that support self-snoop.
As srcu_read_lock() is always called in the VM-Exit path and it internally
has a smp_mb(), call smp_mb__after_srcu_read_lock() to avoid adding a
second fence and make sure smp_mb() is called without dependency on
implementation details of srcu_read_lock().
Cc: Paolo Bonzini <[email protected]>
Cc: Sean Christopherson <[email protected]>
Cc: Kevin Tian <[email protected]>
Signed-off-by: Yan Zhao <[email protected]>
[sean: massage changelog]
Tested-by: Xiangfei Ma <[email protected]>
Tested-by: Yongwei Ma <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions