summaryrefslogtreecommitdiffstats
path: root/Kconfig
diff options
context:
space:
mode:
authorBen Widawsky <ben@bwidawsk.net>2012-06-04 14:42:43 -0700
committerDaniel Vetter <daniel.vetter@ffwll.ch>2012-06-14 17:36:16 +0200
commit40521054fd46f94e0368cead312d56e9e442aaab (patch)
tree14c220ee426bccd22124b9dd0f5688cde5362a7f /Kconfig
parent254f965c39e3918544395f4ebac8c589d890bae6 (diff)
downloadblackbird-op-linux-40521054fd46f94e0368cead312d56e9e442aaab.tar.gz
blackbird-op-linux-40521054fd46f94e0368cead312d56e9e442aaab.zip
drm/i915: context basic create & destroy
Invent an abstraction for a hw context which is passed around through the core functions. The main bit a hw context holds is the buffer object which backs the context. The rest of the members are just helper functions. Specifically the ring member, which could likely go away if we decide to never implement whatever other hw context support exists. Of note here is the introduction of the 64k alignment constraint for the BO. If contexts become heavily used, we should consider tweaking this down to 4k. Until the contexts are merged and tested a bit though, I think 64k is a nice start (based on docs). Since we don't yet switch contexts, there is really not much complexity here. Creation/destruction works pretty much as one would expect. An idr is used to generate the context id numbers which are unique per file descriptor. v2: add DRM_DEBUG_DRIVERS to distinguish ENOMEM failures (ben) convert a BUG_ON to WARN_ON, default destruction is still fatal (ben) Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud