mirror of
https://github.com/torvalds/linux.git
synced 2024-12-29 06:12:08 +00:00
254f965c39
Very basic code for context setup/destruction in the driver. Adds the file i915_gem_context.c This file implements HW context support. On gen5+ a HW context consists of an opaque GPU object which is referenced at times of context saves and restores. With RC6 enabled, the context is also referenced as the GPU enters and exists from RC6 (GPU has it's own internal power context, except on gen5). Though something like a context does exist for the media ring, the code only supports contexts for the render ring. In software, there is a distinction between contexts created by the user, and the default HW context. The default HW context is used by GPU clients that do not request setup of their own hardware context. The default context's state is never restored to help prevent programming errors. This would happen if a client ran and piggy-backed off another clients GPU state. The default context only exists to give the GPU some offset to load as the current to invoke a save of the context we actually care about. In fact, the code could likely be constructed, albeit in a more complicated fashion, to never use the default context, though that limits the driver's ability to swap out, and/or destroy other contexts. All other contexts are created as a request by the GPU client. These contexts store GPU state, and thus allow GPU clients to not re-emit state (and potentially query certain state) at any time. The kernel driver makes certain that the appropriate commands are inserted. There are 4 entry points into the contexts, init, fini, open, close. The names are self-explanatory except that init can be called during reset, and also during pm thaw/resume. As we expect our context to be preserved across these events, we do not reinitialize in this case. As Adam Jackson pointed out, The cutoff of 1MB where a HW context is considered too big is arbitrary. The reason for this is even though context sizes are increasing with every generation, they have yet to eclipse even 32k. If we somehow read back way more than that, it probably means BIOS has done something strange, or we're running on a platform that wasn't designed for this. v2: rename load/unload to init/fini (daniel) remove ILK support for get_size() (indirectly daniel) add HAS_HW_CONTEXTS macro to clarify supported platforms (daniel) added comments (Ben) Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
52 lines
1.1 KiB
Makefile
52 lines
1.1 KiB
Makefile
#
|
|
# Makefile for the drm device driver. This driver provides support for the
|
|
# Direct Rendering Infrastructure (DRI) in XFree86 4.1.0 and higher.
|
|
|
|
ccflags-y := -Iinclude/drm
|
|
i915-y := i915_drv.o i915_dma.o i915_irq.o \
|
|
i915_debugfs.o \
|
|
i915_suspend.o \
|
|
i915_gem.o \
|
|
i915_gem_context.o \
|
|
i915_gem_debug.o \
|
|
i915_gem_evict.o \
|
|
i915_gem_execbuffer.o \
|
|
i915_gem_gtt.o \
|
|
i915_gem_stolen.o \
|
|
i915_gem_tiling.o \
|
|
i915_sysfs.o \
|
|
i915_trace_points.o \
|
|
intel_display.o \
|
|
intel_crt.o \
|
|
intel_lvds.o \
|
|
intel_bios.o \
|
|
intel_ddi.o \
|
|
intel_dp.o \
|
|
intel_hdmi.o \
|
|
intel_sdvo.o \
|
|
intel_modes.o \
|
|
intel_panel.o \
|
|
intel_pm.o \
|
|
intel_i2c.o \
|
|
intel_fb.o \
|
|
intel_tv.o \
|
|
intel_dvo.o \
|
|
intel_ringbuffer.o \
|
|
intel_overlay.o \
|
|
intel_sprite.o \
|
|
intel_opregion.o \
|
|
dvo_ch7xxx.o \
|
|
dvo_ch7017.o \
|
|
dvo_ivch.o \
|
|
dvo_tfp410.o \
|
|
dvo_sil164.o \
|
|
i915_gem_dmabuf.o
|
|
|
|
i915-$(CONFIG_COMPAT) += i915_ioc32.o
|
|
|
|
i915-$(CONFIG_ACPI) += intel_acpi.o
|
|
|
|
obj-$(CONFIG_DRM_I915) += i915.o
|
|
|
|
CFLAGS_i915_trace_points.o := -I$(src)
|