mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-08-24 01:41:39 +00:00
92581f9fb9
If the caller allows and we do not have to wait for any signals, immediately execute the work within the caller's process. By doing so we avoid the overhead of scheduling a new task, and the latency in executing it, at the cost of pulling that work back into the immediate context. (Sometimes we still prefer to offload the task to another cpu, especially if we plan on executing many such tasks in parallel for this client.) Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20200325120227.8044-2-chris@chris-wilson.co.uk
67 lines
1.7 KiB
C
67 lines
1.7 KiB
C
/* SPDX-License-Identifier: MIT */
|
|
|
|
/*
|
|
* Copyright © 2019 Intel Corporation
|
|
*/
|
|
|
|
#ifndef I915_SW_FENCE_WORK_H
|
|
#define I915_SW_FENCE_WORK_H
|
|
|
|
#include <linux/dma-fence.h>
|
|
#include <linux/spinlock.h>
|
|
#include <linux/workqueue.h>
|
|
|
|
#include "i915_sw_fence.h"
|
|
|
|
struct dma_fence_work;
|
|
|
|
struct dma_fence_work_ops {
|
|
const char *name;
|
|
int (*work)(struct dma_fence_work *f);
|
|
void (*release)(struct dma_fence_work *f);
|
|
};
|
|
|
|
struct dma_fence_work {
|
|
struct dma_fence dma;
|
|
spinlock_t lock;
|
|
|
|
struct i915_sw_fence chain;
|
|
struct i915_sw_dma_fence_cb cb;
|
|
|
|
struct work_struct work;
|
|
const struct dma_fence_work_ops *ops;
|
|
};
|
|
|
|
enum {
|
|
DMA_FENCE_WORK_IMM = DMA_FENCE_FLAG_USER_BITS,
|
|
};
|
|
|
|
void dma_fence_work_init(struct dma_fence_work *f,
|
|
const struct dma_fence_work_ops *ops);
|
|
int dma_fence_work_chain(struct dma_fence_work *f, struct dma_fence *signal);
|
|
|
|
static inline void dma_fence_work_commit(struct dma_fence_work *f)
|
|
{
|
|
i915_sw_fence_commit(&f->chain);
|
|
}
|
|
|
|
/**
|
|
* dma_fence_work_commit_imm: Commit the fence, and if possible execute locally.
|
|
* @f: the fenced worker
|
|
*
|
|
* Instead of always scheduling a worker to execute the callback (see
|
|
* dma_fence_work_commit()), we try to execute the callback immediately in
|
|
* the local context. It is required that the fence be committed before it
|
|
* is published, and that no other threads try to tamper with the number
|
|
* of asynchronous waits on the fence (or else the callback will be
|
|
* executed in the wrong context, i.e. not the callers).
|
|
*/
|
|
static inline void dma_fence_work_commit_imm(struct dma_fence_work *f)
|
|
{
|
|
if (atomic_read(&f->chain.pending) <= 1)
|
|
__set_bit(DMA_FENCE_WORK_IMM, &f->dma.flags);
|
|
|
|
dma_fence_work_commit(f);
|
|
}
|
|
|
|
#endif /* I915_SW_FENCE_WORK_H */
|