drm/xe/pvc: Use fast copy engines as migrate engine on PVC
authorNiranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Thu, 17 Aug 2023 05:14:10 +0000 (22:14 -0700)
committerRodrigo Vivi <rodrigo.vivi@intel.com>
Thu, 21 Dec 2023 16:40:28 +0000 (11:40 -0500)
commita043fbab7af54c64017269dc96f43f441ed4bcaf
tree42a9057b459288d0866ea0f0832ee4437ac13823
parent7407f2e5c356a73ec4a6d7f379e91f205025165c
drm/xe/pvc: Use fast copy engines as migrate engine on PVC

Some copy hardware engine instances are faster than others on PVC.
Use a virtual engine of these plus the reserved instance for the migrate
engine on PVC. The idea being if a fast instance is available it will be
used and the throughput of kernel copies, clears, and pagefault
servicing will be higher.

v2: Use OOB WA, use all copy engines if no WA is required

Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
drivers/gpu/drm/xe/Makefile
drivers/gpu/drm/xe/xe_migrate.c
drivers/gpu/drm/xe/xe_wa_oob.rules