diff options
author | 2016-11-07 10:44:36 +0800 | |
---|---|---|
committer | 2016-11-10 15:39:46 +0800 | |
commit | 9baf0920b5d8e4e4ea302cb954168e06cf838d63 (patch) | |
tree | e662d2830a63900086fbe2637c176a7aa83c3682 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | Merge tag 'for-kvmgt' of git://git.kernel.org/pub/scm/virt/kvm/kvm into drm-intel-next-queued (diff) | |
download | linux-dev-9baf0920b5d8e4e4ea302cb954168e06cf838d63.tar.xz linux-dev-9baf0920b5d8e4e4ea302cb954168e06cf838d63.zip |
drm/i915/gvt: don't rely on guest PPGTT entry to free old shadow data
On guest writing a PPGTT entry, if it contains value and the old
entry is valid, gvt will read it and find & free the corresponding
old data for it. However, with the KVM write protection provided
by page_track, the guest entry will be written with new value
before gvt handling. To avoid that, we should use the shadow
entry instead.
Signed-off-by: Bing Niu <bing.niu@intel.com>
Signed-off-by: Jike Song <jike.song@intel.com>
Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions