aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorChris Wilson <[email protected]>2012-06-04 17:05:40 +0100
committerDaniel Vetter <[email protected]>2012-06-04 20:16:40 +0200
commit3eef8918ff440837f6af791942d8dd07e1a268ee (patch)
treee32d25574d4e9cc80ec0b1060c17f0c6dec346f6 /tools/perf/util/scripting-engines/trace-event-python.c
parent9e612a008fa7fe493a473454def56aa321479495 (diff)
drm/i915: Mark the ringbuffers as being in the GTT domain
By correctly describing the rinbuffers as being in the GTT domain, it appears that we are more careful with the management of the CPU cache upon resume and so prevent some coherency issue when submitting commands to the GPU later. A secondary effect is that the debug logs are then consistent with the actual usage (i.e. they no longer describe the ringbuffers as being in the CPU write domain when we are accessing them through an wc iomapping.) Reported-and-tested-by: Daniel Gnoutcheff <[email protected]> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=41092 Signed-off-by: Chris Wilson <[email protected]> Cc: [email protected] Signed-off-by: Daniel Vetter <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions