diff options
| author | Tvrtko Ursulin <tvrtko.ursulin@intel.com> | 2017-03-10 09:57:47 +0000 |
|---|---|---|
| committer | Tvrtko Ursulin <tvrtko.ursulin@intel.com> | 2017-03-17 09:52:57 +0000 |
| commit | e3b1895fc1d29ebd8a8e3374fc076f138a1f8f4b (patch) | |
| tree | 7d220721ed8946f42eac04648f45ba3b5cfc5356 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | fa7e8b55e939468c2988cd01f893348f5d36ed0a (diff) | |
drm/i915/vgpu: Neuter forcewakes for VGPU more thoroughly
If we avoid initializing forcewake domains when running as
a guest, and also use gen2 mmio accessors in that case, we
can avoid the timer traffic and any looping through the
forcewake code which is currently just so it can end up in
the no-op forcewake implementation.
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: Weinan Li <weinan.z.li@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Tested-by: Terrence Xu <terrence.xu@intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20170310095747.12258-1-tvrtko.ursulin@linux.intel.com
[tursulin: commit spelling fix]
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions