drm/xe/pvc: Use fast copy engines as migrate engine on PVC

Browse source

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>

...

This commit is contained in:

Niranjana Vishwanathapura 2023-08-16 22:14:10 -07:00 • committed by Rodrigo Vivi

parent 7407f2e5c3

commit a043fbab7a

3 changed files with 34 additions and 5 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

drivers/gpu/drm/xe/Makefile

View file

36

drivers/gpu/drm/xe/xe_migrate.c

View file

1

drivers/gpu/drm/xe/xe_wa_oob.rules

View file