Lines Matching defs:context
30 * fence context counter: each execution context should have its own
31 * fence context, this allows checking if fences belong to the same
32 * context or not. One device can have multiple separate contexts,
45 * dma_fence_signal(). Fences are associated with a context, allocated through
46 * dma_fence_context_alloc(), and all fences on the same context are
79 * affects the offending userspace context, and no other userspace
146 * allocated. The fence context is used for setting &dma_fence.context to a
147 * unique number by passing the context to dma_fence_init().
235 * both in interrupt and process context. Due to implementation details this
502 fence->ops->get_timeline_name(fence), fence->context, fence->seqno)) {
596 * Note that the callback can be called from an atomic context. If
605 * itself can be called from irq context.
889 * @context: the execution context this fence is run on
890 * @seqno: a linear increasing sequence number for this context
896 * context and seqno are used for easy comparison between fences, allowing
899 void dma_fence_init(struct dma_fence *fence, const struct dma_fence_ops *ops, spinlock_t *lock, u64 context, u64 seqno)
908 fence->context = context;