diff options
| author | Sean Christopherson <[email protected]> | 2023-07-28 18:35:23 -0700 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2023-08-31 14:07:24 -0400 |
| commit | 2ee05a4c275a54d9b64599bcbf7117a9490c9e43 (patch) | |
| tree | 42b64ae2ee0d59c313f150710962221e507f1378 /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | c70934e0ab2d2c4bb16bf70c3e3db8c064a1761b (diff) | |
drm/i915/gvt: Don't bother removing write-protection on to-be-deleted slot
When handling a slot "flush", don't call back into KVM to drop write
protection for gfns in the slot. Now that KVM rejects attempts to move
memory slots while KVMGT is attached, the only time a slot is "flushed"
is when it's being removed, i.e. the memslot and all its write-tracking
metadata is about to be deleted.
Reviewed-by: Yan Zhao <[email protected]>
Tested-by: Yongwei Ma <[email protected]>
Reviewed-by: Zhi Wang <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions