diff options
| author | Yan Zhao <[email protected]> | 2023-07-28 18:35:25 -0700 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2023-08-31 14:07:25 -0400 |
| commit | c15fcf12ffb37be314752202fb02cf16138e66fb (patch) | |
| tree | 56a378ce5db11222a054b78c2a356f554f5a2ffe /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | b83ab124ded3c17f911668522a2e916ca8d3c523 (diff) | |
drm/i915/gvt: switch from ->track_flush_slot() to ->track_remove_region()
Switch from the poorly named and flawed ->track_flush_slot() to the newly
introduced ->track_remove_region(). From KVMGT's perspective, the two
hooks are functionally equivalent, the only difference being that
->track_remove_region() is called only when KVM is 100% certain the
memory region will be removed, i.e. is invoked slightly later in KVM's
memslot modification flow.
Cc: Zhenyu Wang <[email protected]>
Suggested-by: Sean Christopherson <[email protected]>
Signed-off-by: Yan Zhao <[email protected]>
[sean: handle name change, massage changelog, rebase]
Tested-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