From: sashiko-bot@kernel.org
To: "Leon Romanovsky" <leon@kernel.org>
Cc: media-ci@linuxtv.org, dri-devel@lists.freedesktop.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 2/2] dma-buf: Document how exporters and importers agree on mapping lifetime
Date: Tue, 25 Aug 2026 06:31:11 +0000 [thread overview]
Message-ID: <20260825063112.453D41F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260825-document-dma-buf-v1-2-5ecfb3e1371c@nvidia.com>
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Pinned, revoked and movable mappings are selected by which optional
> callbacks each side implements and by whether dma_buf_pin() succeeds,
> not by any flag or enum. Nothing in Documentation/ says so, and the
> rules are spread over the kdoc of dma_buf_ops.pin,
> dma_buf_attach_ops.invalidate_mappings and dma_buf_invalidate_mappings(),
> so a driver author has to know the symbol names before finding them.
>
> Name, per flow, the callbacks both sides have to implement to end up in
> it, describe dma_buf_pin() as the runtime negotiation, and record that
> the pin is what tells a revoke from a move.
>
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260825-document-dma-buf-v1-0-5ecfb3e1371c@nvidia.com?part=2
next prev parent reply other threads:[~2026-08-25 6:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 6:28 [PATCH 0/2] Document the DMA-buf mapping lifetime negotiation Leon Romanovsky
2026-08-25 6:28 ` [PATCH 1/2] PCI/P2PDMA: Update DMABUF lifecycle docs after move_notify() rename Leon Romanovsky
2026-08-25 6:29 ` sashiko-bot
2026-08-25 20:05 ` Logan Gunthorpe
2026-08-26 11:50 ` Christian König
2026-09-03 20:34 ` Bjorn Helgaas
2026-09-04 6:40 ` Leon Romanovsky
2026-08-25 6:28 ` [PATCH 2/2] dma-buf: Document how exporters and importers agree on mapping lifetime Leon Romanovsky
2026-08-25 6:31 ` sashiko-bot [this message]
2026-08-26 11:41 ` Christian König
2026-08-26 12:43 ` Leon Romanovsky
2026-08-26 13:06 ` Christian König
2026-08-26 14:02 ` Leon Romanovsky
2026-08-31 9:22 ` Christian König
2026-09-01 14:08 ` Jason Gunthorpe
2026-08-27 19:18 ` [Linaro-mm-sig] " Thomas Hellström
2026-08-30 7:58 ` Leon Romanovsky
2026-08-31 6:39 ` Thomas Hellström
2026-08-31 8:56 ` Christian König
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=20260825063112.453D41F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=leon@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=media-ci@linuxtv.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.