diff options
| author | Chris Wilson <chris@chris-wilson.co.uk> | 2019-07-30 14:21:51 +0300 |
|---|---|---|
| committer | Chris Wilson <chris@chris-wilson.co.uk> | 2019-08-02 10:38:45 +0300 |
| commit | 576f05865581f82ac988ffec70e4e2ebd31165db (patch) | |
| tree | 48c1c5940b49864a83e88cadcf6a9582986ddf6f /security | |
| parent | 51fbd8de87dcf09f3929e5438e4344bea4338990 (diff) | |
| download | linux-576f05865581f82ac988ffec70e4e2ebd31165db.tar.xz | |
drm/i915: Flush extra hard after writing relocations through the GTT
Recently discovered in commit bdae33b8b82b ("drm/i915: Use maximum write
flush for pwrite_gtt") was that we needed to our full write barrier
before changing the GGTT PTE to ensure that our indirect writes through
the GTT landed before the PTE changed (and the writes end up in a
different page). That also applies to our GGTT relocation path.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: stable@vger.kernel.org
Reviewed-by: Prathap Kumar Valsan <prathap.kumar.valsan@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20190730112151.5633-4-chris@chris-wilson.co.uk
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions