diff options
| author |   Chris Wilson <chris@chris-wilson.co.uk> | 2015-04-07 16:20:33 +0100 |
|---|---|---|
| committer |   Daniel Vetter <daniel.vetter@ffwll.ch> | 2015-04-10 08:56:03 +0200 |
| commit | 7c27f52509994a874371a0756bee35facf51858b (patch) | |
| tree | 125c98f3ef953d99d05a4bd69dc602b7deeb5217 /drivers/gpu/drm/i915/i915_gem_batch_pool.c | |
| parent | drm/i915: Deminish contribution of wait-boosting from clients (diff) | |
| download | linux-dev-7c27f52509994a874371a0756bee35facf51858b.tar.xz linux-dev-7c27f52509994a874371a0756bee35facf51858b.zip | |
drm/i915: Re-enable RPS wait-boosting for all engines
This reverts commit ec5cc0f9b019af95e4571a9fa162d94294c8d90b
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Thu Jun 12 10:28:55 2014 +0100
drm/i915: Restrict GPU boost to the RCS engine
The premise that media/blitter workloads are not affected by boosting is
patently false with a trip through igt. The question that remains is
what exactly is going wrong with the media workload that prompted this?
Hopefully that would be fixed by the missing agressive downclocking, in
addition to the extra restrictions imposed on how frequent a process is
allowed to boost.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Deepak S <deepak.s@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll>
Acked-by: Deepak S <deepak.s@linux.intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'drivers/gpu/drm/i915/i915_gem_batch_pool.c')
0 files changed, 0 insertions, 0 deletions