diff options
| author | Colin Xu <colin.xu@intel.com> | 2018-08-17 10:42:24 +0200 |
|---|---|---|
| committer | Zhenyu Wang <zhenyuw@linux.intel.com> | 2018-08-30 06:54:09 +0200 |
| commit | b9b824a55876275f8506c1c187558ab22d879f73 (patch) | |
| tree | 8bdb47fe57b05dbb02e88f0e064e04535cf3dee4 /drivers/gpu/drm/i915/i915_oa_sklgt4.h | |
| parent | drm/i915/gvt: Make correct handling to vreg BXT_PHY_CTL_FAMILY (diff) | |
| download | linux-b9b824a55876275f8506c1c187558ab22d879f73.tar.xz linux-b9b824a55876275f8506c1c187558ab22d879f73.zip | |
drm/i915/gvt: Handle GEN9_WM_CHICKEN3 with F_CMD_ACCESS.
Recent patch introduce strict check on scanning cmd:
Commit 8d458ea0ec33 ("drm/i915/gvt: return error on cmd access")
Before 8d458ea0ec33, if cmd_reg_handler() checks that a cmd access a mmio
that not marked as F_CMD_ACCESS, it simply returns 0 and log an error.
Now it will return -EBADRQC which will cause the workload fail to submit.
On BXT, i915 applies WaClearHIZ_WM_CHICKEN3 which will program
GEN9_WM_CHICKEN3 by LRI when init wa ctx. If it has no F_CMD_ACCESS flag,
vgpu will fail to start. Also add F_MODE_MASK since it's mode mask reg.
v2: Refresh commit message to elaborate issue symptom in detail.
v3: Make SKL_PLUS share same handling since GEN9_WM_CHICKEN3 should be
F_CMD_ACCESS from HW aspect. (yan, zhenyu)
Signed-off-by: Colin Xu <colin.xu@intel.com>
Acked-by: Zhao Yan <yan.y.zhao@intel.com>
Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Diffstat (limited to 'drivers/gpu/drm/i915/i915_oa_sklgt4.h')
0 files changed, 0 insertions, 0 deletions