summaryrefslogtreecommitdiffstats
path: root/mm/swap_state.c
diff options
context:
space:
mode:
authorChangbin Du <changbin.du@intel.com>2017-03-22 12:35:31 +0800
committerZhenyu Wang <zhenyuw@linux.intel.com>2017-03-22 13:18:56 +0800
commitbc2d4b62db67f817b09c782219996630e9c2f5e2 (patch)
tree1e9800f79a9250fc5c60d7909330d577e32ad48d /mm/swap_state.c
parent359b69310014511901bd61cc5f7680cb5de1faef (diff)
downloadop-kernel-dev-bc2d4b62db67f817b09c782219996630e9c2f5e2.zip
op-kernel-dev-bc2d4b62db67f817b09c782219996630e9c2f5e2.tar.gz
drm/i915/gvt: Use force single submit flag to distinguish gvt request from i915 request
In my previous Commit ab9da627906a ("drm/i915: make context status notifier head be per engine") rely on scheduler->current_workload[x] to distinguish gvt spacial request from i915 request. But this is not always true since no synchronization between workload_thread and lrc irq handler. lrc irq handler workload_thread ---- ---- pick i915 requests; intel_vgpu_submit_execlist(); current_workload[x] = xxx; shadow_context_status_change(); Then current_workload[x] is not null but current request is of i915 self. So instead we check ctx flag CONTEXT_FORCE_SINGLE_SUBMISSION. Only gvt request set this flag and always set. v2: Reverse the order of multi-condition 'if' statement. Fixes: ab9da6279 ("drm/i915: make context status notifier head be per engine") Signed-off-by: Changbin Du <changbin.du@intel.com> Reviewed-by: Yulei Zhang <yulei.zhang@intel.com> Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Diffstat (limited to 'mm/swap_state.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud