2010-05-21 09:08:55 +08:00
|
|
|
#ifndef _INTEL_RINGBUFFER_H_
|
|
|
|
#define _INTEL_RINGBUFFER_H_
|
|
|
|
|
2014-05-11 05:10:43 +08:00
|
|
|
#include <linux/hashtable.h>
|
2015-04-07 23:20:36 +08:00
|
|
|
#include "i915_gem_batch_pool.h"
|
2014-05-11 05:10:43 +08:00
|
|
|
|
|
|
|
#define I915_CMD_HASH_ORDER 9
|
|
|
|
|
2014-07-25 00:04:28 +08:00
|
|
|
/* Early gen2 devices have a cacheline of just 32 bytes, using 64 is overkill,
|
|
|
|
* but keeps the logic simple. Indeed, the whole purpose of this macro is just
|
|
|
|
* to give some inclination as to some of the magic values used in the various
|
|
|
|
* workarounds!
|
|
|
|
*/
|
|
|
|
#define CACHELINE_BYTES 64
|
2015-06-20 02:07:01 +08:00
|
|
|
#define CACHELINE_DWORDS (CACHELINE_BYTES / sizeof(uint32_t))
|
2014-07-25 00:04:28 +08:00
|
|
|
|
2012-12-04 00:43:32 +08:00
|
|
|
/*
|
|
|
|
* Gen2 BSpec "1. Programming Environment" / 1.4.4.6 "Ring Buffer Use"
|
|
|
|
* Gen3 BSpec "vol1c Memory Interface Functions" / 2.3.4.5 "Ring Buffer Use"
|
|
|
|
* Gen4+ BSpec "vol1c Memory Interface and Command Stream" / 5.3.4.5 "Ring Buffer Use"
|
|
|
|
*
|
|
|
|
* "If the Ring Buffer Head Pointer and the Tail Pointer are on the same
|
|
|
|
* cacheline, the Head Pointer must not be greater than the Tail
|
|
|
|
* Pointer."
|
|
|
|
*/
|
|
|
|
#define I915_RING_FREE_SPACE 64
|
|
|
|
|
2010-05-21 09:08:55 +08:00
|
|
|
struct intel_hw_status_page {
|
2012-04-27 05:28:16 +08:00
|
|
|
u32 *page_addr;
|
2010-05-21 09:08:55 +08:00
|
|
|
unsigned int gfx_addr;
|
2010-11-09 03:18:58 +08:00
|
|
|
struct drm_i915_gem_object *obj;
|
2010-05-21 09:08:55 +08:00
|
|
|
};
|
|
|
|
|
2011-04-26 02:22:22 +08:00
|
|
|
#define I915_READ_TAIL(ring) I915_READ(RING_TAIL((ring)->mmio_base))
|
|
|
|
#define I915_WRITE_TAIL(ring, val) I915_WRITE(RING_TAIL((ring)->mmio_base), val)
|
2010-11-09 17:17:32 +08:00
|
|
|
|
2011-04-26 02:22:22 +08:00
|
|
|
#define I915_READ_START(ring) I915_READ(RING_START((ring)->mmio_base))
|
|
|
|
#define I915_WRITE_START(ring, val) I915_WRITE(RING_START((ring)->mmio_base), val)
|
2010-11-09 17:17:32 +08:00
|
|
|
|
2011-04-26 02:22:22 +08:00
|
|
|
#define I915_READ_HEAD(ring) I915_READ(RING_HEAD((ring)->mmio_base))
|
|
|
|
#define I915_WRITE_HEAD(ring, val) I915_WRITE(RING_HEAD((ring)->mmio_base), val)
|
2010-11-09 17:17:32 +08:00
|
|
|
|
2011-04-26 02:22:22 +08:00
|
|
|
#define I915_READ_CTL(ring) I915_READ(RING_CTL((ring)->mmio_base))
|
|
|
|
#define I915_WRITE_CTL(ring, val) I915_WRITE(RING_CTL((ring)->mmio_base), val)
|
2010-11-09 17:17:32 +08:00
|
|
|
|
2011-04-26 02:22:22 +08:00
|
|
|
#define I915_READ_IMR(ring) I915_READ(RING_IMR((ring)->mmio_base))
|
|
|
|
#define I915_WRITE_IMR(ring, val) I915_WRITE(RING_IMR((ring)->mmio_base), val)
|
2010-08-02 22:29:44 +08:00
|
|
|
|
2014-03-12 19:09:41 +08:00
|
|
|
#define I915_READ_MODE(ring) I915_READ(RING_MI_MODE((ring)->mmio_base))
|
2014-04-02 23:36:07 +08:00
|
|
|
#define I915_WRITE_MODE(ring, val) I915_WRITE(RING_MI_MODE((ring)->mmio_base), val)
|
2014-03-12 19:09:41 +08:00
|
|
|
|
2014-07-01 00:53:37 +08:00
|
|
|
/* seqno size is actually only a uint32, but since we plan to use MI_FLUSH_DW to
|
|
|
|
* do the writes, and that must have qw aligned offsets, simply pretend it's 8b.
|
|
|
|
*/
|
|
|
|
#define i915_semaphore_seqno_size sizeof(uint64_t)
|
|
|
|
#define GEN8_SIGNAL_OFFSET(__ring, to) \
|
|
|
|
(i915_gem_obj_ggtt_offset(dev_priv->semaphore_obj) + \
|
|
|
|
((__ring)->id * I915_NUM_RINGS * i915_semaphore_seqno_size) + \
|
|
|
|
(i915_semaphore_seqno_size * (to)))
|
|
|
|
|
|
|
|
#define GEN8_WAIT_OFFSET(__ring, from) \
|
|
|
|
(i915_gem_obj_ggtt_offset(dev_priv->semaphore_obj) + \
|
|
|
|
((from) * I915_NUM_RINGS * i915_semaphore_seqno_size) + \
|
|
|
|
(i915_semaphore_seqno_size * (__ring)->id))
|
|
|
|
|
|
|
|
#define GEN8_RING_SEMAPHORE_INIT do { \
|
|
|
|
if (!dev_priv->semaphore_obj) { \
|
|
|
|
break; \
|
|
|
|
} \
|
|
|
|
ring->semaphore.signal_ggtt[RCS] = GEN8_SIGNAL_OFFSET(ring, RCS); \
|
|
|
|
ring->semaphore.signal_ggtt[VCS] = GEN8_SIGNAL_OFFSET(ring, VCS); \
|
|
|
|
ring->semaphore.signal_ggtt[BCS] = GEN8_SIGNAL_OFFSET(ring, BCS); \
|
|
|
|
ring->semaphore.signal_ggtt[VECS] = GEN8_SIGNAL_OFFSET(ring, VECS); \
|
|
|
|
ring->semaphore.signal_ggtt[VCS2] = GEN8_SIGNAL_OFFSET(ring, VCS2); \
|
|
|
|
ring->semaphore.signal_ggtt[ring->id] = MI_SEMAPHORE_SYNC_INVALID; \
|
|
|
|
} while(0)
|
|
|
|
|
2013-08-11 17:44:01 +08:00
|
|
|
enum intel_ring_hangcheck_action {
|
2013-09-06 21:03:28 +08:00
|
|
|
HANGCHECK_IDLE = 0,
|
2013-08-11 17:44:01 +08:00
|
|
|
HANGCHECK_WAIT,
|
|
|
|
HANGCHECK_ACTIVE,
|
2014-08-05 22:16:26 +08:00
|
|
|
HANGCHECK_ACTIVE_LOOP,
|
2013-08-11 17:44:01 +08:00
|
|
|
HANGCHECK_KICK,
|
|
|
|
HANGCHECK_HUNG,
|
|
|
|
};
|
2013-06-12 17:35:32 +08:00
|
|
|
|
2014-01-31 01:04:43 +08:00
|
|
|
#define HANGCHECK_SCORE_RING_HUNG 31
|
|
|
|
|
2013-05-24 22:16:07 +08:00
|
|
|
struct intel_ring_hangcheck {
|
2014-03-21 20:41:53 +08:00
|
|
|
u64 acthd;
|
2014-08-05 22:16:26 +08:00
|
|
|
u64 max_acthd;
|
2013-05-24 22:16:07 +08:00
|
|
|
u32 seqno;
|
2013-05-30 14:04:29 +08:00
|
|
|
int score;
|
2013-06-12 17:35:32 +08:00
|
|
|
enum intel_ring_hangcheck_action action;
|
2014-06-06 17:22:29 +08:00
|
|
|
int deadlock;
|
2013-05-24 22:16:07 +08:00
|
|
|
};
|
|
|
|
|
2014-05-22 21:13:34 +08:00
|
|
|
struct intel_ringbuffer {
|
|
|
|
struct drm_i915_gem_object *obj;
|
|
|
|
void __iomem *virtual_start;
|
|
|
|
|
2014-08-11 22:17:44 +08:00
|
|
|
struct intel_engine_cs *ring;
|
2015-09-03 20:01:40 +08:00
|
|
|
struct list_head link;
|
2014-08-11 22:17:44 +08:00
|
|
|
|
2014-05-22 21:13:34 +08:00
|
|
|
u32 head;
|
|
|
|
u32 tail;
|
|
|
|
int space;
|
|
|
|
int size;
|
|
|
|
int effective_size;
|
drm/i915: Reserve ring buffer space for i915_add_request() commands
It is a bad idea for i915_add_request() to fail. The work will already have been
send to the ring and will be processed, but there will not be any tracking or
management of that work.
The only way the add request call can fail is if it can't write its epilogue
commands to the ring (cache flushing, seqno updates, interrupt signalling). The
reasons for that are mostly down to running out of ring buffer space and the
problems associated with trying to get some more. This patch prevents that
situation from happening in the first place.
When a request is created, it marks sufficient space as reserved for the
epilogue commands. Thus guaranteeing that by the time the epilogue is written,
there will be plenty of space for it. Note that a ring_begin() call is required
to actually reserve the space (and do any potential waiting). However, that is
not currently done at request creation time. This is because the ring_begin()
code can allocate a request. Hence calling begin() from the request allocation
code would lead to infinite recursion! Later patches in this series remove the
need for begin() to do the allocate. At that point, it becomes safe for the
allocate to call begin() and really reserve the space.
Until then, there is a potential for insufficient space to be available at the
point of calling i915_add_request(). However, that would only be in the case
where the request was created and immediately submitted without ever calling
ring_begin() and adding any work to that request. Which should never happen. And
even if it does, and if that request happens to fall down the tiny window of
opportunity for failing due to being out of ring space then does it really
matter because the request wasn't doing anything in the first place?
v2: Updated the 'reserved space too small' warning to include the offending
sizes. Added a 'cancel' operation to clean up when a request is abandoned. Added
re-initialisation of tracking state after a buffer wrap to keep the sanity
checks accurate.
v3: Incremented the reserved size to accommodate Ironlake (after finally
managing to run on an ILK system). Also fixed missing wrap code in LRC mode.
v4: Added extra comment and removed duplicate WARN (feedback from Tomas).
For: VIZ-5115
CC: Tomas Elf <tomas.elf@intel.com>
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2015-06-18 20:10:09 +08:00
|
|
|
int reserved_size;
|
|
|
|
int reserved_tail;
|
|
|
|
bool reserved_in_use;
|
2014-05-22 21:13:34 +08:00
|
|
|
|
|
|
|
/** We track the position of the requests in the ring buffer, and
|
|
|
|
* when each is retired we increment last_retired_head as the GPU
|
|
|
|
* must have finished processing the request and so we know we
|
|
|
|
* can advance the ringbuffer up to that position.
|
|
|
|
*
|
|
|
|
* last_retired_head is set to -1 after the value is consumed so
|
|
|
|
* we can detect new retirements.
|
|
|
|
*/
|
|
|
|
u32 last_retired_head;
|
|
|
|
};
|
|
|
|
|
2015-01-15 21:10:38 +08:00
|
|
|
struct intel_context;
|
2015-05-29 21:44:14 +08:00
|
|
|
struct drm_i915_reg_descriptor;
|
2015-01-15 21:10:38 +08:00
|
|
|
|
2015-06-20 02:07:01 +08:00
|
|
|
/*
|
|
|
|
* we use a single page to load ctx workarounds so all of these
|
|
|
|
* values are referred in terms of dwords
|
|
|
|
*
|
|
|
|
* struct i915_wa_ctx_bb:
|
|
|
|
* offset: specifies batch starting position, also helpful in case
|
|
|
|
* if we want to have multiple batches at different offsets based on
|
|
|
|
* some criteria. It is not a requirement at the moment but provides
|
|
|
|
* an option for future use.
|
|
|
|
* size: size of the batch in DWORDS
|
|
|
|
*/
|
|
|
|
struct i915_ctx_workarounds {
|
|
|
|
struct i915_wa_ctx_bb {
|
|
|
|
u32 offset;
|
|
|
|
u32 size;
|
|
|
|
} indirect_ctx, per_ctx;
|
|
|
|
struct drm_i915_gem_object *obj;
|
|
|
|
};
|
|
|
|
|
2014-05-22 21:13:33 +08:00
|
|
|
struct intel_engine_cs {
|
2010-05-21 09:08:55 +08:00
|
|
|
const char *name;
|
2010-09-18 18:02:01 +08:00
|
|
|
enum intel_ring_id {
|
2011-12-14 20:57:00 +08:00
|
|
|
RCS = 0x0,
|
|
|
|
VCS,
|
|
|
|
BCS,
|
2013-05-29 10:22:19 +08:00
|
|
|
VECS,
|
2014-04-17 10:37:37 +08:00
|
|
|
VCS2
|
2010-09-18 18:02:01 +08:00
|
|
|
} id;
|
2014-04-17 10:37:37 +08:00
|
|
|
#define I915_NUM_RINGS 5
|
2014-04-17 10:37:36 +08:00
|
|
|
#define LAST_USER_RING (VECS + 1)
|
2010-08-02 22:24:01 +08:00
|
|
|
u32 mmio_base;
|
2010-05-21 09:08:55 +08:00
|
|
|
struct drm_device *dev;
|
2014-05-22 21:13:34 +08:00
|
|
|
struct intel_ringbuffer *buffer;
|
2015-09-03 20:01:40 +08:00
|
|
|
struct list_head buffers;
|
2010-05-21 09:08:55 +08:00
|
|
|
|
2015-04-07 23:20:36 +08:00
|
|
|
/*
|
|
|
|
* A pool of objects to use as shadow copies of client batch buffers
|
|
|
|
* when the command parser is enabled. Prevents the client from
|
|
|
|
* modifying the batch contents after software parsing.
|
|
|
|
*/
|
|
|
|
struct i915_gem_batch_pool batch_pool;
|
|
|
|
|
2010-05-21 09:08:55 +08:00
|
|
|
struct intel_hw_status_page status_page;
|
2015-06-20 02:07:01 +08:00
|
|
|
struct i915_ctx_workarounds wa_ctx;
|
2010-05-21 09:08:55 +08:00
|
|
|
|
2013-07-05 05:35:29 +08:00
|
|
|
unsigned irq_refcount; /* protected by dev_priv->irq_lock */
|
2012-04-12 04:12:46 +08:00
|
|
|
u32 irq_enable_mask; /* bitmask to enable ring interrupt */
|
2014-11-25 02:49:39 +08:00
|
|
|
struct drm_i915_gem_request *trace_irq_req;
|
2014-05-22 21:13:33 +08:00
|
|
|
bool __must_check (*irq_get)(struct intel_engine_cs *ring);
|
|
|
|
void (*irq_put)(struct intel_engine_cs *ring);
|
2010-05-21 09:08:55 +08:00
|
|
|
|
2014-11-20 07:33:04 +08:00
|
|
|
int (*init_hw)(struct intel_engine_cs *ring);
|
2010-05-21 09:08:55 +08:00
|
|
|
|
2015-05-30 00:43:44 +08:00
|
|
|
int (*init_context)(struct drm_i915_gem_request *req);
|
2014-08-26 21:44:50 +08:00
|
|
|
|
2014-05-22 21:13:33 +08:00
|
|
|
void (*write_tail)(struct intel_engine_cs *ring,
|
2010-10-23 00:02:41 +08:00
|
|
|
u32 value);
|
2015-05-30 00:43:57 +08:00
|
|
|
int __must_check (*flush)(struct drm_i915_gem_request *req,
|
2011-01-05 01:34:02 +08:00
|
|
|
u32 invalidate_domains,
|
|
|
|
u32 flush_domains);
|
2015-05-30 00:44:00 +08:00
|
|
|
int (*add_request)(struct drm_i915_gem_request *req);
|
2012-08-09 17:58:30 +08:00
|
|
|
/* Some chipsets are not quite as coherent as advertised and need
|
|
|
|
* an expensive kick to force a true read of the up-to-date seqno.
|
|
|
|
* However, the up-to-date seqno is not always required and the last
|
|
|
|
* seen value is good enough. Note that the seqno will always be
|
|
|
|
* monotonic, even if not coherent.
|
|
|
|
*/
|
2014-05-22 21:13:33 +08:00
|
|
|
u32 (*get_seqno)(struct intel_engine_cs *ring,
|
2012-08-09 17:58:30 +08:00
|
|
|
bool lazy_coherency);
|
2014-05-22 21:13:33 +08:00
|
|
|
void (*set_seqno)(struct intel_engine_cs *ring,
|
2012-12-19 17:13:05 +08:00
|
|
|
u32 seqno);
|
2015-05-30 00:44:02 +08:00
|
|
|
int (*dispatch_execbuffer)(struct drm_i915_gem_request *req,
|
2014-04-29 10:29:25 +08:00
|
|
|
u64 offset, u32 length,
|
2015-02-13 19:48:10 +08:00
|
|
|
unsigned dispatch_flags);
|
2012-10-17 19:09:54 +08:00
|
|
|
#define I915_DISPATCH_SECURE 0x1
|
2012-12-17 23:21:27 +08:00
|
|
|
#define I915_DISPATCH_PINNED 0x2
|
2015-06-16 18:39:40 +08:00
|
|
|
#define I915_DISPATCH_RS 0x4
|
2014-05-22 21:13:33 +08:00
|
|
|
void (*cleanup)(struct intel_engine_cs *ring);
|
2014-04-30 05:52:28 +08:00
|
|
|
|
2014-07-01 00:53:37 +08:00
|
|
|
/* GEN8 signal/wait table - never trust comments!
|
|
|
|
* signal to signal to signal to signal to signal to
|
|
|
|
* RCS VCS BCS VECS VCS2
|
|
|
|
* --------------------------------------------------------------------
|
|
|
|
* RCS | NOP (0x00) | VCS (0x08) | BCS (0x10) | VECS (0x18) | VCS2 (0x20) |
|
|
|
|
* |-------------------------------------------------------------------
|
|
|
|
* VCS | RCS (0x28) | NOP (0x30) | BCS (0x38) | VECS (0x40) | VCS2 (0x48) |
|
|
|
|
* |-------------------------------------------------------------------
|
|
|
|
* BCS | RCS (0x50) | VCS (0x58) | NOP (0x60) | VECS (0x68) | VCS2 (0x70) |
|
|
|
|
* |-------------------------------------------------------------------
|
|
|
|
* VECS | RCS (0x78) | VCS (0x80) | BCS (0x88) | NOP (0x90) | VCS2 (0x98) |
|
|
|
|
* |-------------------------------------------------------------------
|
|
|
|
* VCS2 | RCS (0xa0) | VCS (0xa8) | BCS (0xb0) | VECS (0xb8) | NOP (0xc0) |
|
|
|
|
* |-------------------------------------------------------------------
|
|
|
|
*
|
|
|
|
* Generalization:
|
|
|
|
* f(x, y) := (x->id * NUM_RINGS * seqno_size) + (seqno_size * y->id)
|
|
|
|
* ie. transpose of g(x, y)
|
|
|
|
*
|
|
|
|
* sync from sync from sync from sync from sync from
|
|
|
|
* RCS VCS BCS VECS VCS2
|
|
|
|
* --------------------------------------------------------------------
|
|
|
|
* RCS | NOP (0x00) | VCS (0x28) | BCS (0x50) | VECS (0x78) | VCS2 (0xa0) |
|
|
|
|
* |-------------------------------------------------------------------
|
|
|
|
* VCS | RCS (0x08) | NOP (0x30) | BCS (0x58) | VECS (0x80) | VCS2 (0xa8) |
|
|
|
|
* |-------------------------------------------------------------------
|
|
|
|
* BCS | RCS (0x10) | VCS (0x38) | NOP (0x60) | VECS (0x88) | VCS2 (0xb0) |
|
|
|
|
* |-------------------------------------------------------------------
|
|
|
|
* VECS | RCS (0x18) | VCS (0x40) | BCS (0x68) | NOP (0x90) | VCS2 (0xb8) |
|
|
|
|
* |-------------------------------------------------------------------
|
|
|
|
* VCS2 | RCS (0x20) | VCS (0x48) | BCS (0x70) | VECS (0x98) | NOP (0xc0) |
|
|
|
|
* |-------------------------------------------------------------------
|
|
|
|
*
|
|
|
|
* Generalization:
|
|
|
|
* g(x, y) := (y->id * NUM_RINGS * seqno_size) + (seqno_size * x->id)
|
|
|
|
* ie. transpose of f(x, y)
|
|
|
|
*/
|
2014-04-30 05:52:28 +08:00
|
|
|
struct {
|
|
|
|
u32 sync_seqno[I915_NUM_RINGS-1];
|
2014-04-30 05:52:29 +08:00
|
|
|
|
2014-07-01 00:53:37 +08:00
|
|
|
union {
|
|
|
|
struct {
|
|
|
|
/* our mbox written by others */
|
|
|
|
u32 wait[I915_NUM_RINGS];
|
|
|
|
/* mboxes this ring signals to */
|
drm/i915: Type safe register read/write
Make I915_READ and I915_WRITE more type safe by wrapping the register
offset in a struct. This should eliminate most of the fumbles we've had
with misplaced parens.
This only takes care of normal mmio registers. We could extend the idea
to other register types and define each with its own struct. That way
you wouldn't be able to accidentally pass the wrong thing to a specific
register access function.
The gpio_reg setup is probably the ugliest thing left. But I figure I'd
just leave it for now, and wait for some divine inspiration to strike
before making it nice.
As for the generated code, it's actually a bit better sometimes. Eg.
looking at i915_irq_handler(), we can see the following change:
lea 0x70024(%rdx,%rax,1),%r9d
mov $0x1,%edx
- movslq %r9d,%r9
- mov %r9,%rsi
- mov %r9,-0x58(%rbp)
- callq *0xd8(%rbx)
+ mov %r9d,%esi
+ mov %r9d,-0x48(%rbp)
callq *0xd8(%rbx)
So previously gcc thought the register offset might be signed and
decided to sign extend it, just in case. The rest appears to be
mostly just minor shuffling of instructions.
v2: i915_mmio_reg_{offset,equal,valid}() helpers added
s/_REG/_MMIO/ in the register defines
mo more switch statements left to worry about
ring_emit stuff got sorted in a prep patch
cmd parser, lrc context and w/a batch buildup also in prep patch
vgpu stuff cleaned up and moved to a prep patch
all other unrelated changes split out
v3: Rebased due to BXT DSI/BLC, MOCS, etc.
v4: Rebased due to churn, s/i915_mmio_reg_t/i915_reg_t/
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Link: http://patchwork.freedesktop.org/patch/msgid/1447853606-2751-1-git-send-email-ville.syrjala@linux.intel.com
2015-11-18 21:33:26 +08:00
|
|
|
i915_reg_t signal[I915_NUM_RINGS];
|
2014-07-01 00:53:37 +08:00
|
|
|
} mbox;
|
|
|
|
u64 signal_ggtt[I915_NUM_RINGS];
|
|
|
|
};
|
2014-04-30 05:52:29 +08:00
|
|
|
|
|
|
|
/* AKA wait() */
|
2015-05-30 00:44:04 +08:00
|
|
|
int (*sync_to)(struct drm_i915_gem_request *to_req,
|
|
|
|
struct intel_engine_cs *from,
|
2014-04-30 05:52:29 +08:00
|
|
|
u32 seqno);
|
2015-05-30 00:44:05 +08:00
|
|
|
int (*signal)(struct drm_i915_gem_request *signaller_req,
|
2014-04-30 05:52:30 +08:00
|
|
|
/* num_dwords needed by caller */
|
|
|
|
unsigned int num_dwords);
|
2014-04-30 05:52:28 +08:00
|
|
|
} semaphore;
|
2013-05-29 10:22:18 +08:00
|
|
|
|
2014-07-25 00:04:27 +08:00
|
|
|
/* Execlists */
|
2014-07-25 00:04:38 +08:00
|
|
|
spinlock_t execlist_lock;
|
|
|
|
struct list_head execlist_queue;
|
2014-11-13 18:27:05 +08:00
|
|
|
struct list_head execlist_retired_req_list;
|
drm/i915/bdw: Handle context switch events
Handle all context status events in the context status buffer on every
context switch interrupt. We only remove work from the execlist queue
after a context status buffer reports that it has completed and we only
attempt to schedule new contexts on interrupt when a previously submitted
context completes (unless no contexts are queued, which means the GPU is
free).
We canot call intel_runtime_pm_get() in an interrupt (or with a spinlock
grabbed, FWIW), because it might sleep, which is not a nice thing to do.
Instead, do the runtime_pm get/put together with the create/destroy request,
and handle the forcewake get/put directly.
Signed-off-by: Thomas Daniel <thomas.daniel@intel.com>
v2: Unreferencing the context when we are freeing the request might free
the backing bo, which requires the struct_mutex to be grabbed, so defer
unreferencing and freeing to a bottom half.
v3:
- Ack the interrupt inmediately, before trying to handle it (fix for
missing interrupts by Bob Beckett <robert.beckett@intel.com>).
- Update the Context Status Buffer Read Pointer, just in case (spotted
by Damien Lespiau).
v4: New namespace and multiple rebase changes.
v5: Squash with "drm/i915/bdw: Do not call intel_runtime_pm_get() in an
interrupt", as suggested by Daniel.
Signed-off-by: Oscar Mateo <oscar.mateo@intel.com>
Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>
[danvet: Checkpatch ...]
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2014-07-25 00:04:39 +08:00
|
|
|
u8 next_context_status_buffer;
|
2014-07-25 00:04:31 +08:00
|
|
|
u32 irq_keep_mask; /* bitmask for interrupts that should not be masked */
|
2015-05-30 00:44:01 +08:00
|
|
|
int (*emit_request)(struct drm_i915_gem_request *request);
|
2015-05-30 00:43:59 +08:00
|
|
|
int (*emit_flush)(struct drm_i915_gem_request *request,
|
2014-07-25 00:04:28 +08:00
|
|
|
u32 invalidate_domains,
|
|
|
|
u32 flush_domains);
|
2015-05-30 00:44:03 +08:00
|
|
|
int (*emit_bb_start)(struct drm_i915_gem_request *req,
|
2015-02-13 19:48:10 +08:00
|
|
|
u64 offset, unsigned dispatch_flags);
|
2014-07-25 00:04:27 +08:00
|
|
|
|
2010-05-21 09:08:55 +08:00
|
|
|
/**
|
|
|
|
* List of objects currently involved in rendering from the
|
|
|
|
* ringbuffer.
|
|
|
|
*
|
|
|
|
* Includes buffers having the contents of their GPU caches
|
2014-11-25 02:49:26 +08:00
|
|
|
* flushed, not necessarily primitives. last_read_req
|
2010-05-21 09:08:55 +08:00
|
|
|
* represents when the rendering involved will be completed.
|
|
|
|
*
|
|
|
|
* A reference is held on the buffer while on this list.
|
|
|
|
*/
|
|
|
|
struct list_head active_list;
|
|
|
|
|
|
|
|
/**
|
|
|
|
* List of breadcrumbs associated with GPU requests currently
|
|
|
|
* outstanding.
|
|
|
|
*/
|
|
|
|
struct list_head request_list;
|
|
|
|
|
2015-07-09 22:30:57 +08:00
|
|
|
/**
|
|
|
|
* Seqno of request most recently submitted to request_list.
|
|
|
|
* Used exclusively by hang checker to avoid grabbing lock while
|
|
|
|
* inspecting request list.
|
|
|
|
*/
|
|
|
|
u32 last_submitted_seqno;
|
|
|
|
|
2012-06-14 02:45:19 +08:00
|
|
|
bool gpu_caches_dirty;
|
2010-09-28 17:07:56 +08:00
|
|
|
|
2010-05-21 09:08:55 +08:00
|
|
|
wait_queue_head_t irq_queue;
|
2010-11-02 16:31:01 +08:00
|
|
|
|
2014-05-22 21:13:37 +08:00
|
|
|
struct intel_context *default_context;
|
|
|
|
struct intel_context *last_context;
|
2012-06-05 05:42:43 +08:00
|
|
|
|
2013-05-24 22:16:07 +08:00
|
|
|
struct intel_ring_hangcheck hangcheck;
|
|
|
|
|
2013-08-27 03:58:11 +08:00
|
|
|
struct {
|
|
|
|
struct drm_i915_gem_object *obj;
|
|
|
|
u32 gtt_offset;
|
|
|
|
volatile u32 *cpu_page;
|
|
|
|
} scratch;
|
2014-02-19 02:15:46 +08:00
|
|
|
|
2014-05-11 05:10:43 +08:00
|
|
|
bool needs_cmd_parser;
|
|
|
|
|
2014-02-19 02:15:46 +08:00
|
|
|
/*
|
2014-05-11 05:10:43 +08:00
|
|
|
* Table of commands the command parser needs to know about
|
2014-02-19 02:15:46 +08:00
|
|
|
* for this ring.
|
|
|
|
*/
|
2014-05-11 05:10:43 +08:00
|
|
|
DECLARE_HASHTABLE(cmd_hash, I915_CMD_HASH_ORDER);
|
2014-02-19 02:15:46 +08:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Table of registers allowed in commands that read/write registers.
|
|
|
|
*/
|
2015-05-29 21:44:14 +08:00
|
|
|
const struct drm_i915_reg_descriptor *reg_table;
|
2014-02-19 02:15:46 +08:00
|
|
|
int reg_count;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Table of registers allowed in commands that read/write registers, but
|
|
|
|
* only from the DRM master.
|
|
|
|
*/
|
2015-05-29 21:44:14 +08:00
|
|
|
const struct drm_i915_reg_descriptor *master_reg_table;
|
2014-02-19 02:15:46 +08:00
|
|
|
int master_reg_count;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Returns the bitmask for the length field of the specified command.
|
|
|
|
* Return 0 for an unrecognized/invalid command.
|
|
|
|
*
|
|
|
|
* If the command parser finds an entry for a command in the ring's
|
|
|
|
* cmd_tables, it gets the command's length based on the table entry.
|
|
|
|
* If not, it calls this function to determine the per-ring length field
|
|
|
|
* encoding for the command (i.e. certain opcode ranges use certain bits
|
|
|
|
* to encode the command length in the header).
|
|
|
|
*/
|
|
|
|
u32 (*get_cmd_length_mask)(u32 cmd_header);
|
2010-05-21 09:08:55 +08:00
|
|
|
};
|
|
|
|
|
2015-12-08 23:02:36 +08:00
|
|
|
static inline bool
|
|
|
|
intel_ring_initialized(struct intel_engine_cs *ring)
|
|
|
|
{
|
|
|
|
return ring->dev != NULL;
|
|
|
|
}
|
2012-05-11 21:29:30 +08:00
|
|
|
|
2011-12-14 20:57:00 +08:00
|
|
|
static inline unsigned
|
2014-05-22 21:13:33 +08:00
|
|
|
intel_ring_flag(struct intel_engine_cs *ring)
|
2011-12-14 20:57:00 +08:00
|
|
|
{
|
|
|
|
return 1 << ring->id;
|
|
|
|
}
|
|
|
|
|
2010-12-04 19:30:53 +08:00
|
|
|
static inline u32
|
2014-05-22 21:13:33 +08:00
|
|
|
intel_ring_sync_index(struct intel_engine_cs *ring,
|
|
|
|
struct intel_engine_cs *other)
|
2010-12-04 19:30:53 +08:00
|
|
|
{
|
|
|
|
int idx;
|
|
|
|
|
|
|
|
/*
|
2014-07-01 00:51:11 +08:00
|
|
|
* rcs -> 0 = vcs, 1 = bcs, 2 = vecs, 3 = vcs2;
|
|
|
|
* vcs -> 0 = bcs, 1 = vecs, 2 = vcs2, 3 = rcs;
|
|
|
|
* bcs -> 0 = vecs, 1 = vcs2. 2 = rcs, 3 = vcs;
|
|
|
|
* vecs -> 0 = vcs2, 1 = rcs, 2 = vcs, 3 = bcs;
|
|
|
|
* vcs2 -> 0 = rcs, 1 = vcs, 2 = bcs, 3 = vecs;
|
2010-12-04 19:30:53 +08:00
|
|
|
*/
|
|
|
|
|
|
|
|
idx = (other - ring) - 1;
|
|
|
|
if (idx < 0)
|
|
|
|
idx += I915_NUM_RINGS;
|
|
|
|
|
|
|
|
return idx;
|
|
|
|
}
|
|
|
|
|
2015-08-14 23:35:27 +08:00
|
|
|
static inline void
|
|
|
|
intel_flush_status_page(struct intel_engine_cs *ring, int reg)
|
|
|
|
{
|
|
|
|
drm_clflush_virt_range(&ring->status_page.page_addr[reg],
|
|
|
|
sizeof(uint32_t));
|
|
|
|
}
|
|
|
|
|
2010-05-21 09:08:55 +08:00
|
|
|
static inline u32
|
2014-05-22 21:13:33 +08:00
|
|
|
intel_read_status_page(struct intel_engine_cs *ring,
|
2010-10-27 19:18:21 +08:00
|
|
|
int reg)
|
2010-05-21 09:08:55 +08:00
|
|
|
{
|
2012-04-27 05:28:16 +08:00
|
|
|
/* Ensure that the compiler doesn't optimize away the load. */
|
|
|
|
barrier();
|
|
|
|
return ring->status_page.page_addr[reg];
|
2010-05-21 09:08:55 +08:00
|
|
|
}
|
|
|
|
|
2012-12-19 17:13:05 +08:00
|
|
|
static inline void
|
2014-05-22 21:13:33 +08:00
|
|
|
intel_write_status_page(struct intel_engine_cs *ring,
|
2012-12-19 17:13:05 +08:00
|
|
|
int reg, u32 value)
|
|
|
|
{
|
|
|
|
ring->status_page.page_addr[reg] = value;
|
|
|
|
}
|
|
|
|
|
2011-01-14 03:06:50 +08:00
|
|
|
/**
|
|
|
|
* Reads a dword out of the status page, which is written to from the command
|
|
|
|
* queue by automatic updates, MI_REPORT_HEAD, MI_STORE_DATA_INDEX, or
|
|
|
|
* MI_STORE_DATA_IMM.
|
|
|
|
*
|
|
|
|
* The following dwords have a reserved meaning:
|
|
|
|
* 0x00: ISR copy, updated when an ISR bit not set in the HWSTAM changes.
|
|
|
|
* 0x04: ring 0 head pointer
|
|
|
|
* 0x05: ring 1 head pointer (915-class)
|
|
|
|
* 0x06: ring 2 head pointer (915-class)
|
|
|
|
* 0x10-0x1b: Context status DWords (GM45)
|
|
|
|
* 0x1f: Last written status offset. (GM45)
|
2015-02-18 19:48:21 +08:00
|
|
|
* 0x20-0x2f: Reserved (Gen6+)
|
2011-01-14 03:06:50 +08:00
|
|
|
*
|
2015-02-18 19:48:21 +08:00
|
|
|
* The area from dword 0x30 to 0x3ff is available for driver usage.
|
2011-01-14 03:06:50 +08:00
|
|
|
*/
|
2015-02-18 19:48:21 +08:00
|
|
|
#define I915_GEM_HWS_INDEX 0x30
|
|
|
|
#define I915_GEM_HWS_SCRATCH_INDEX 0x40
|
2012-10-27 00:42:42 +08:00
|
|
|
#define I915_GEM_HWS_SCRATCH_ADDR (I915_GEM_HWS_SCRATCH_INDEX << MI_STORE_DWORD_INDEX_SHIFT)
|
2011-01-14 03:06:50 +08:00
|
|
|
|
2015-09-03 20:01:39 +08:00
|
|
|
struct intel_ringbuffer *
|
|
|
|
intel_engine_create_ringbuffer(struct intel_engine_cs *engine, int size);
|
2014-11-13 18:28:56 +08:00
|
|
|
int intel_pin_and_map_ringbuffer_obj(struct drm_device *dev,
|
|
|
|
struct intel_ringbuffer *ringbuf);
|
2015-09-03 20:01:39 +08:00
|
|
|
void intel_unpin_ringbuffer_obj(struct intel_ringbuffer *ringbuf);
|
|
|
|
void intel_ringbuffer_free(struct intel_ringbuffer *ring);
|
2014-07-25 00:04:15 +08:00
|
|
|
|
2014-05-22 21:13:33 +08:00
|
|
|
void intel_stop_ring_buffer(struct intel_engine_cs *ring);
|
|
|
|
void intel_cleanup_ring_buffer(struct intel_engine_cs *ring);
|
2011-03-20 09:14:27 +08:00
|
|
|
|
2015-03-19 20:30:08 +08:00
|
|
|
int intel_ring_alloc_request_extras(struct drm_i915_gem_request *request);
|
|
|
|
|
2015-05-30 00:44:07 +08:00
|
|
|
int __must_check intel_ring_begin(struct drm_i915_gem_request *req, int n);
|
2015-05-30 00:44:06 +08:00
|
|
|
int __must_check intel_ring_cacheline_align(struct drm_i915_gem_request *req);
|
2014-05-22 21:13:33 +08:00
|
|
|
static inline void intel_ring_emit(struct intel_engine_cs *ring,
|
2010-10-27 19:18:21 +08:00
|
|
|
u32 data)
|
2010-08-04 22:18:14 +08:00
|
|
|
{
|
2014-05-22 21:13:36 +08:00
|
|
|
struct intel_ringbuffer *ringbuf = ring->buffer;
|
|
|
|
iowrite32(data, ringbuf->virtual_start + ringbuf->tail);
|
|
|
|
ringbuf->tail += 4;
|
2010-08-04 22:18:14 +08:00
|
|
|
}
|
2015-11-05 05:20:07 +08:00
|
|
|
static inline void intel_ring_emit_reg(struct intel_engine_cs *ring,
|
drm/i915: Type safe register read/write
Make I915_READ and I915_WRITE more type safe by wrapping the register
offset in a struct. This should eliminate most of the fumbles we've had
with misplaced parens.
This only takes care of normal mmio registers. We could extend the idea
to other register types and define each with its own struct. That way
you wouldn't be able to accidentally pass the wrong thing to a specific
register access function.
The gpio_reg setup is probably the ugliest thing left. But I figure I'd
just leave it for now, and wait for some divine inspiration to strike
before making it nice.
As for the generated code, it's actually a bit better sometimes. Eg.
looking at i915_irq_handler(), we can see the following change:
lea 0x70024(%rdx,%rax,1),%r9d
mov $0x1,%edx
- movslq %r9d,%r9
- mov %r9,%rsi
- mov %r9,-0x58(%rbp)
- callq *0xd8(%rbx)
+ mov %r9d,%esi
+ mov %r9d,-0x48(%rbp)
callq *0xd8(%rbx)
So previously gcc thought the register offset might be signed and
decided to sign extend it, just in case. The rest appears to be
mostly just minor shuffling of instructions.
v2: i915_mmio_reg_{offset,equal,valid}() helpers added
s/_REG/_MMIO/ in the register defines
mo more switch statements left to worry about
ring_emit stuff got sorted in a prep patch
cmd parser, lrc context and w/a batch buildup also in prep patch
vgpu stuff cleaned up and moved to a prep patch
all other unrelated changes split out
v3: Rebased due to BXT DSI/BLC, MOCS, etc.
v4: Rebased due to churn, s/i915_mmio_reg_t/i915_reg_t/
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Link: http://patchwork.freedesktop.org/patch/msgid/1447853606-2751-1-git-send-email-ville.syrjala@linux.intel.com
2015-11-18 21:33:26 +08:00
|
|
|
i915_reg_t reg)
|
2015-11-05 05:20:07 +08:00
|
|
|
{
|
drm/i915: Type safe register read/write
Make I915_READ and I915_WRITE more type safe by wrapping the register
offset in a struct. This should eliminate most of the fumbles we've had
with misplaced parens.
This only takes care of normal mmio registers. We could extend the idea
to other register types and define each with its own struct. That way
you wouldn't be able to accidentally pass the wrong thing to a specific
register access function.
The gpio_reg setup is probably the ugliest thing left. But I figure I'd
just leave it for now, and wait for some divine inspiration to strike
before making it nice.
As for the generated code, it's actually a bit better sometimes. Eg.
looking at i915_irq_handler(), we can see the following change:
lea 0x70024(%rdx,%rax,1),%r9d
mov $0x1,%edx
- movslq %r9d,%r9
- mov %r9,%rsi
- mov %r9,-0x58(%rbp)
- callq *0xd8(%rbx)
+ mov %r9d,%esi
+ mov %r9d,-0x48(%rbp)
callq *0xd8(%rbx)
So previously gcc thought the register offset might be signed and
decided to sign extend it, just in case. The rest appears to be
mostly just minor shuffling of instructions.
v2: i915_mmio_reg_{offset,equal,valid}() helpers added
s/_REG/_MMIO/ in the register defines
mo more switch statements left to worry about
ring_emit stuff got sorted in a prep patch
cmd parser, lrc context and w/a batch buildup also in prep patch
vgpu stuff cleaned up and moved to a prep patch
all other unrelated changes split out
v3: Rebased due to BXT DSI/BLC, MOCS, etc.
v4: Rebased due to churn, s/i915_mmio_reg_t/i915_reg_t/
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Link: http://patchwork.freedesktop.org/patch/msgid/1447853606-2751-1-git-send-email-ville.syrjala@linux.intel.com
2015-11-18 21:33:26 +08:00
|
|
|
intel_ring_emit(ring, i915_mmio_reg_offset(reg));
|
2015-11-05 05:20:07 +08:00
|
|
|
}
|
2014-05-22 21:13:33 +08:00
|
|
|
static inline void intel_ring_advance(struct intel_engine_cs *ring)
|
2013-08-11 05:16:32 +08:00
|
|
|
{
|
2014-05-22 21:13:36 +08:00
|
|
|
struct intel_ringbuffer *ringbuf = ring->buffer;
|
|
|
|
ringbuf->tail &= ringbuf->size - 1;
|
2013-08-11 05:16:32 +08:00
|
|
|
}
|
2014-07-25 00:04:26 +08:00
|
|
|
int __intel_ring_space(int head, int tail, int size);
|
2014-11-27 19:22:49 +08:00
|
|
|
void intel_ring_update_space(struct intel_ringbuffer *ringbuf);
|
2014-07-25 00:04:26 +08:00
|
|
|
int intel_ring_space(struct intel_ringbuffer *ringbuf);
|
|
|
|
bool intel_ring_stopped(struct intel_engine_cs *ring);
|
2013-08-11 05:16:32 +08:00
|
|
|
|
2014-05-22 21:13:33 +08:00
|
|
|
int __must_check intel_ring_idle(struct intel_engine_cs *ring);
|
|
|
|
void intel_ring_init_seqno(struct intel_engine_cs *ring, u32 seqno);
|
2015-05-30 00:43:55 +08:00
|
|
|
int intel_ring_flush_all_caches(struct drm_i915_gem_request *req);
|
2015-05-30 00:43:53 +08:00
|
|
|
int intel_ring_invalidate_all_caches(struct drm_i915_gem_request *req);
|
2010-05-21 09:08:55 +08:00
|
|
|
|
2014-07-25 00:04:24 +08:00
|
|
|
void intel_fini_pipe_control(struct intel_engine_cs *ring);
|
|
|
|
int intel_init_pipe_control(struct intel_engine_cs *ring);
|
|
|
|
|
2010-09-16 10:43:11 +08:00
|
|
|
int intel_init_render_ring_buffer(struct drm_device *dev);
|
|
|
|
int intel_init_bsd_ring_buffer(struct drm_device *dev);
|
2014-04-17 10:37:37 +08:00
|
|
|
int intel_init_bsd2_ring_buffer(struct drm_device *dev);
|
2010-10-19 18:19:32 +08:00
|
|
|
int intel_init_blt_ring_buffer(struct drm_device *dev);
|
2013-05-29 10:22:23 +08:00
|
|
|
int intel_init_vebox_ring_buffer(struct drm_device *dev);
|
2010-05-21 09:08:55 +08:00
|
|
|
|
2014-05-22 21:13:33 +08:00
|
|
|
u64 intel_ring_get_active_head(struct intel_engine_cs *ring);
|
2010-09-25 03:20:10 +08:00
|
|
|
|
2014-11-12 00:47:33 +08:00
|
|
|
int init_workarounds_ring(struct intel_engine_cs *ring);
|
|
|
|
|
2014-07-03 23:28:04 +08:00
|
|
|
static inline u32 intel_ring_get_tail(struct intel_ringbuffer *ringbuf)
|
2012-02-15 19:25:36 +08:00
|
|
|
{
|
2014-07-03 23:28:04 +08:00
|
|
|
return ringbuf->tail;
|
2012-02-15 19:25:36 +08:00
|
|
|
}
|
|
|
|
|
drm/i915: Reserve ring buffer space for i915_add_request() commands
It is a bad idea for i915_add_request() to fail. The work will already have been
send to the ring and will be processed, but there will not be any tracking or
management of that work.
The only way the add request call can fail is if it can't write its epilogue
commands to the ring (cache flushing, seqno updates, interrupt signalling). The
reasons for that are mostly down to running out of ring buffer space and the
problems associated with trying to get some more. This patch prevents that
situation from happening in the first place.
When a request is created, it marks sufficient space as reserved for the
epilogue commands. Thus guaranteeing that by the time the epilogue is written,
there will be plenty of space for it. Note that a ring_begin() call is required
to actually reserve the space (and do any potential waiting). However, that is
not currently done at request creation time. This is because the ring_begin()
code can allocate a request. Hence calling begin() from the request allocation
code would lead to infinite recursion! Later patches in this series remove the
need for begin() to do the allocate. At that point, it becomes safe for the
allocate to call begin() and really reserve the space.
Until then, there is a potential for insufficient space to be available at the
point of calling i915_add_request(). However, that would only be in the case
where the request was created and immediately submitted without ever calling
ring_begin() and adding any work to that request. Which should never happen. And
even if it does, and if that request happens to fall down the tiny window of
opportunity for failing due to being out of ring space then does it really
matter because the request wasn't doing anything in the first place?
v2: Updated the 'reserved space too small' warning to include the offending
sizes. Added a 'cancel' operation to clean up when a request is abandoned. Added
re-initialisation of tracking state after a buffer wrap to keep the sanity
checks accurate.
v3: Incremented the reserved size to accommodate Ironlake (after finally
managing to run on an ILK system). Also fixed missing wrap code in LRC mode.
v4: Added extra comment and removed duplicate WARN (feedback from Tomas).
For: VIZ-5115
CC: Tomas Elf <tomas.elf@intel.com>
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2015-06-18 20:10:09 +08:00
|
|
|
/*
|
|
|
|
* Arbitrary size for largest possible 'add request' sequence. The code paths
|
|
|
|
* are complex and variable. Empirical measurement shows that the worst case
|
|
|
|
* is ILK at 136 words. Reserving too much is better than reserving too little
|
|
|
|
* as that allows for corner cases that might have been missed. So the figure
|
|
|
|
* has been rounded up to 160 words.
|
|
|
|
*/
|
|
|
|
#define MIN_SPACE_FOR_ADD_REQUEST 160
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Reserve space in the ring to guarantee that the i915_add_request() call
|
|
|
|
* will always have sufficient room to do its stuff. The request creation
|
|
|
|
* code calls this automatically.
|
|
|
|
*/
|
|
|
|
void intel_ring_reserved_space_reserve(struct intel_ringbuffer *ringbuf, int size);
|
|
|
|
/* Cancel the reservation, e.g. because the request is being discarded. */
|
|
|
|
void intel_ring_reserved_space_cancel(struct intel_ringbuffer *ringbuf);
|
|
|
|
/* Use the reserved space - for use by i915_add_request() only. */
|
|
|
|
void intel_ring_reserved_space_use(struct intel_ringbuffer *ringbuf);
|
|
|
|
/* Finish with the reserved space - for use by i915_add_request() only. */
|
|
|
|
void intel_ring_reserved_space_end(struct intel_ringbuffer *ringbuf);
|
|
|
|
|
2015-06-30 19:40:55 +08:00
|
|
|
/* Legacy ringbuffer specific portion of reservation code: */
|
|
|
|
int intel_ring_reserve_space(struct drm_i915_gem_request *request);
|
|
|
|
|
2010-05-21 09:08:55 +08:00
|
|
|
#endif /* _INTEL_RINGBUFFER_H_ */
|