summaryrefslogtreecommitdiff
path: root/include/linux/node.h
diff options
context:
space:
mode:
authorBen Widawsky <ben@bwidawsk.net>2013-12-06 14:11:02 -0800
committerDaniel Vetter <daniel.vetter@ffwll.ch>2013-12-18 15:27:54 +0100
commit0009e46cd54324c4af20b0b52b89973b1b914167 (patch)
treef772771a86a606a310102325ecb86e41ea9f8866 /include/linux/node.h
parent67e3d2979be1bf42d1818b2961c671eb31e0b4d9 (diff)
drm/i915: Track which ring a context ran on
Previously we dropped the association of a context to a ring. It is however very important to know which ring a context ran on (we could have reused the other member, but I was nitpicky). This is very important when we switch address spaces, which unlike context objects, do change per ring. As an example, if we have: RCS BCS ctx A ctx A ctx B ctx B Without tracking the last ring B ran on, we wouldn't know to switch the address space on BCS in the last row. As a result, we no longer need to track which ring a context "belongs" to, as it never really made much sense anyway. Signed-off-by: Ben Widawsky <ben@bwidawsk.net> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'include/linux/node.h')
0 files changed, 0 insertions, 0 deletions