diff options
| author |   Christian König <christian.koenig@amd.com> | 2022-04-04 14:58:37 +0200 |
|---|---|---|
| committer | Christian König <christian.koenig@amd.com> | 2022-04-07 12:53:54 +0200 |
| commit | 8f94eda39952a8c7323bad2bf752bdfe78101b20 (patch) | |
| tree | 005ae7404fd58dcb37d54359f33227a8b79941fc /include/linux/dma-resv.h | |
| parent | drm/ttm: remove bo->moving (diff) | |
| download | linux-dev-8f94eda39952a8c7323bad2bf752bdfe78101b20.tar.xz linux-dev-8f94eda39952a8c7323bad2bf752bdfe78101b20.zip | |
dma-buf: drop seq count based update
This should be possible now since we don't have the distinction
between exclusive and shared fences any more.
The only possible pitfall is that a dma_fence would be reused during the
RCU grace period, but even that could be handled with a single extra check.
Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: https://patchwork.freedesktop.org/patch/msgid/20220407085946.744568-15-christian.koenig@amd.com
Diffstat (limited to 'include/linux/dma-resv.h')
| -rw-r--r-- | include/linux/dma-resv.h | 12 |
1 files changed, 0 insertions, 12 deletions
diff --git a/include/linux/dma-resv.h b/include/linux/dma-resv.h index 1db759eacc98..c8ccbc94d5d2 100644 --- a/include/linux/dma-resv.h +++ b/include/linux/dma-resv.h @@ -156,15 +156,6 @@ struct dma_resv { struct ww_mutex lock; /** - * @seq: - * - * Sequence count for managing RCU read-side synchronization, allows - * read-only access to @fences while ensuring we take a consistent - * snapshot. - */ - seqcount_ww_mutex_t seq; - - /** * @fences: * * Array of fences which where added to the dma_resv object @@ -202,9 +193,6 @@ struct dma_resv_iter { /** @fence_usage: the usage of the current fence */ enum dma_resv_usage fence_usage; - /** @seq: sequence number to check for modifications */ - unsigned int seq; - /** @index: index into the shared fences */ unsigned int index; |