On Mon, 19 Aug 2019 at 17:45, Chris Wilson wrote:
>
> Inside gtt_restore_mappings() we currently take the obj->resv->lock, but
> in the future we need to avoid taking this fs-reclaim tainted lock as we
> need to extend the coverage of the vm->mutex. Take advantage of the
> single-threaded nature
Inside gtt_restore_mappings() we currently take the obj->resv->lock, but
in the future we need to avoid taking this fs-reclaim tainted lock as we
need to extend the coverage of the vm->mutex. Take advantage of the
single-threaded nature of the early resume phase, and do a single
wbinvd() to flush
