From: Daniel Vetter <daniel@ffwll.ch>
To: DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Thomas Hellstrom <thomas.hellstrom@intel.com>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [Intel-gfx] [PATCH] dma-buf: minor doc touch-ups
Date: Wed, 24 Jun 2020 21:32:45 +0200 [thread overview]
Message-ID: <20200624144431.GA3278063@phenom.ffwll.local> (raw)
In-Reply-To: <20200612070535.1778368-1-daniel.vetter@ffwll.ch>
On Fri, Jun 12, 2020 at 09:05:35AM +0200, Daniel Vetter wrote:
> Just some tiny edits:
> - fix link to struct dma_fence
> - give slightly more meaningful title - the polling here is about
> implicit fences, explicit fences (in sync_file or drm_syncobj) also
> have their own polling
>
> v2: I misplaced the .rst include change corresponding to this patch.
>
> Reviewed-by: Thomas Hellstrom <thomas.hellstrom@intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
I went ahead and merged this one, shouldn't be the controversial part of
the series :-)
-Daniel
> ---
> Documentation/driver-api/dma-buf.rst | 6 +++---
> drivers/dma-buf/dma-buf.c | 6 +++---
> 2 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/driver-api/dma-buf.rst b/Documentation/driver-api/dma-buf.rst
> index 63dec76d1d8d..7fb7b661febd 100644
> --- a/Documentation/driver-api/dma-buf.rst
> +++ b/Documentation/driver-api/dma-buf.rst
> @@ -100,11 +100,11 @@ CPU Access to DMA Buffer Objects
> .. kernel-doc:: drivers/dma-buf/dma-buf.c
> :doc: cpu access
>
> -Fence Poll Support
> -~~~~~~~~~~~~~~~~~~
> +Implicit Fence Poll Support
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> .. kernel-doc:: drivers/dma-buf/dma-buf.c
> - :doc: fence polling
> + :doc: implicit fence polling
>
> Kernel Functions and Structures Reference
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.c
> index 01ce125f8e8d..e018ef80451e 100644
> --- a/drivers/dma-buf/dma-buf.c
> +++ b/drivers/dma-buf/dma-buf.c
> @@ -161,11 +161,11 @@ static loff_t dma_buf_llseek(struct file *file, loff_t offset, int whence)
> }
>
> /**
> - * DOC: fence polling
> + * DOC: implicit fence polling
> *
> * To support cross-device and cross-driver synchronization of buffer access
> - * implicit fences (represented internally in the kernel with &struct fence) can
> - * be attached to a &dma_buf. The glue for that and a few related things are
> + * implicit fences (represented internally in the kernel with &struct dma_fence)
> + * can be attached to a &dma_buf. The glue for that and a few related things are
> * provided in the &dma_resv structure.
> *
> * Userspace can query the state of these implicitly tracked fences using poll()
> --
> 2.26.2
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-06-24 19:32 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 8:12 [Intel-gfx] [PATCH 00/18] dma-fence lockdep annotations, round 2 Daniel Vetter
2020-06-04 8:12 ` [Intel-gfx] [PATCH 01/18] mm: Track mmu notifiers in fs_reclaim_acquire/release Daniel Vetter
2020-06-10 12:01 ` Thomas Hellström (Intel)
2020-06-10 12:25 ` Daniel Vetter
2020-06-10 19:41 ` [Intel-gfx] [PATCH] " Daniel Vetter
2020-06-21 17:42 ` Qian Cai
2020-06-21 18:07 ` Daniel Vetter
2020-06-21 20:01 ` Daniel Vetter
2020-06-21 22:09 ` Qian Cai
2020-06-23 16:17 ` Qian Cai
2020-06-23 22:13 ` Daniel Vetter
2020-06-23 22:29 ` Qian Cai
2020-06-23 22:31 ` Dave Chinner
2020-06-23 22:36 ` Daniel Vetter
2020-06-21 17:00 ` [Intel-gfx] [PATCH 01/18] " Qian Cai
2020-06-21 17:28 ` Daniel Vetter
2020-06-21 17:46 ` Qian Cai
2020-06-04 8:12 ` [Intel-gfx] [PATCH 02/18] dma-buf: minor doc touch-ups Daniel Vetter
2020-06-10 13:07 ` Thomas Hellström (Intel)
2020-06-12 7:05 ` [Intel-gfx] [PATCH] " Daniel Vetter
2020-06-24 19:32 ` Daniel Vetter [this message]
2020-06-04 8:12 ` [Intel-gfx] [PATCH 03/18] dma-fence: basic lockdep annotations Daniel Vetter
2020-06-04 8:57 ` Thomas Hellström (Intel)
2020-06-04 9:21 ` Daniel Vetter
2020-06-04 9:26 ` Chris Wilson
2020-06-04 9:36 ` Daniel Vetter
2020-06-05 13:29 ` [Intel-gfx] [PATCH] " Daniel Vetter
2020-06-05 14:30 ` Thomas Hellström (Intel)
2020-06-11 9:57 ` Maarten Lankhorst
2020-06-10 14:21 ` [Intel-gfx] [PATCH 03/18] " Tvrtko Ursulin
2020-06-10 15:17 ` Daniel Vetter
2020-06-11 10:36 ` Tvrtko Ursulin
2020-06-11 11:29 ` Daniel Vetter
2020-06-11 14:29 ` Tvrtko Ursulin
2020-06-11 15:03 ` Daniel Vetter
2020-06-11 8:00 ` Chris Wilson
2020-06-11 8:44 ` Dave Airlie
2020-06-11 9:01 ` Daniel Stone
2020-06-19 8:25 ` Chris Wilson
2020-06-19 8:51 ` Daniel Vetter
2020-06-19 9:13 ` Chris Wilson
2020-06-19 9:43 ` Daniel Vetter
2020-06-19 13:12 ` Chris Wilson
2020-06-22 9:16 ` Daniel Vetter
2020-07-09 7:29 ` Daniel Stone
2020-07-09 8:01 ` Daniel Vetter
2020-06-12 7:06 ` [Intel-gfx] [PATCH] " Daniel Vetter
2020-06-04 8:12 ` [Intel-gfx] [PATCH 04/18] dma-fence: prime " Daniel Vetter
2020-06-11 7:30 ` [Intel-gfx] [Linaro-mm-sig] " Thomas Hellström (Intel)
2020-06-11 8:34 ` Daniel Vetter
[not found] ` <20200611141515.GW6578@ziepe.ca>
2020-06-11 23:35 ` Felix Kuehling
2020-06-12 5:11 ` Daniel Vetter
2020-06-19 18:13 ` Jerome Glisse
2020-06-23 7:39 ` Daniel Vetter
2020-06-23 18:44 ` Felix Kuehling
2020-06-23 19:02 ` Daniel Vetter
2020-06-16 12:07 ` Daniel Vetter
2020-06-17 6:48 ` Daniel Vetter
[not found] ` <20200617152835.GF6578@ziepe.ca>
2020-06-18 15:00 ` Daniel Vetter
[not found] ` <20200618172338.GM6578@ziepe.ca>
2020-06-19 7:22 ` Daniel Vetter
[not found] ` <20200619113934.GN6578@ziepe.ca>
2020-06-19 15:06 ` Daniel Vetter
[not found] ` <20200619151551.GP6578@ziepe.ca>
2020-06-19 16:19 ` Daniel Vetter
[not found] ` <20200619172308.GQ6578@ziepe.ca>
2020-06-19 18:09 ` Jerome Glisse
2020-06-19 19:11 ` Alex Deucher
2020-06-19 19:30 ` Felix Kuehling
2020-06-19 19:40 ` Jerome Glisse
[not found] ` <20200619181849.GR6578@ziepe.ca>
2020-06-19 19:48 ` Felix Kuehling
[not found] ` <20200619195538.GT6578@ziepe.ca>
2020-06-19 20:03 ` Felix Kuehling
2020-06-19 20:31 ` Jerome Glisse
[not found] ` <20200622114617.GU6578@ziepe.ca>
2020-06-22 20:15 ` Jerome Glisse
2020-06-19 20:10 ` Jerome Glisse
2020-06-19 20:43 ` Daniel Vetter
2020-06-19 20:59 ` Jerome Glisse
[not found] ` <20200616145312.GC6578@ziepe.ca>
2020-06-17 7:57 ` Daniel Vetter
[not found] ` <20200617152940.GG6578@ziepe.ca>
2020-06-18 14:42 ` Daniel Vetter
2020-06-12 7:01 ` [Intel-gfx] [PATCH] " Daniel Vetter
2020-06-04 8:12 ` [Intel-gfx] [PATCH 05/18] drm/vkms: Annotate vblank timer Daniel Vetter
2020-06-04 8:12 ` [Intel-gfx] [PATCH 06/18] drm/vblank: Annotate with dma-fence signalling section Daniel Vetter
2020-06-04 8:12 ` [Intel-gfx] [PATCH 07/18] drm/atomic-helper: Add dma-fence annotations Daniel Vetter
2020-06-04 8:12 ` [Intel-gfx] [PATCH 08/18] drm/amdgpu: add dma-fence annotations to atomic commit path Daniel Vetter
2020-06-23 10:51 ` Daniel Vetter
2020-06-04 8:12 ` [Intel-gfx] [PATCH 09/18] drm/scheduler: use dma-fence annotations in main thread Daniel Vetter
2020-06-04 8:12 ` [Intel-gfx] [PATCH 10/18] drm/amdgpu: use dma-fence annotations in cs_submit() Daniel Vetter
2020-06-04 8:12 ` [Intel-gfx] [PATCH 11/18] drm/amdgpu: s/GFP_KERNEL/GFP_ATOMIC in scheduler code Daniel Vetter
2020-06-04 8:12 ` [Intel-gfx] [PATCH 12/18] drm/amdgpu: DC also loves to allocate stuff where it shouldn't Daniel Vetter
2020-06-04 8:12 ` [Intel-gfx] [PATCH 13/18] drm/amdgpu/dc: Stop dma_resv_lock inversion in commit_tail Daniel Vetter
2020-06-05 8:30 ` Pierre-Eric Pelloux-Prayer
2020-06-05 12:41 ` Daniel Vetter
2020-06-04 8:12 ` [Intel-gfx] [PATCH 14/18] drm/scheduler: use dma-fence annotations in tdr work Daniel Vetter
2020-06-04 8:12 ` [Intel-gfx] [PATCH 15/18] drm/amdgpu: use dma-fence annotations for gpu reset code Daniel Vetter
2020-06-04 8:12 ` [Intel-gfx] [PATCH 16/18] Revert "drm/amdgpu: add fbdev suspend/resume on gpu reset" Daniel Vetter
2020-06-04 8:12 ` [Intel-gfx] [PATCH 17/18] drm/amdgpu: gpu recovery does full modesets Daniel Vetter
2020-06-04 8:12 ` [Intel-gfx] [PATCH 18/18] drm/i915: Annotate dma_fence_work Daniel Vetter
2020-06-04 8:55 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for dma-fence lockdep annotations, round 2 Patchwork
2020-06-04 8:57 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-06-04 9:08 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-06-05 13:59 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for dma-fence lockdep annotations, round 2 (rev2) Patchwork
2020-06-05 14:01 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-06-05 14:15 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-06-10 20:20 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for dma-fence lockdep annotations, round 2 (rev3) Patchwork
2020-06-10 20:21 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-06-10 20:35 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-06-12 7:18 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for dma-fence lockdep annotations, round 2 (rev6) Patchwork
2020-06-12 7:19 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-06-12 7:32 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-06-22 10:11 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for dma-fence lockdep annotations, round 2 (rev7) Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200624144431.GA3278063@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.hellstrom@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox