From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
linux-tegra@vger.kernel.org, linux-arm-msm@vger.kernel.org,
kernel@collabora.com, Sumit Semwal <sumit.semwal@linaro.org>,
Benjamin Gaignard <benjamin.gaignard@collabora.com>,
Liam Mark <lmark@codeaurora.org>,
Brian Starkey <Brian.Starkey@arm.com>,
John Stultz <jstultz@google.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Daniel Vetter <daniel@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Tomi Valkeinen <tomba@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Tomasz Figa <tfiga@chromium.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Amol Maheshwari <amahesh@qti.qualcomm.com>,
Emil Velikov <emil.l.velikov@gmail.com>
Subject: Re: [PATCH v2 6/7] dma-buf: Change locking policy for mmap()
Date: Mon, 1 May 2023 18:42:40 +0300 [thread overview]
Message-ID: <14d7ed85-7ab6-04d9-1958-d5ceae2a79f8@collabora.com> (raw)
In-Reply-To: <20230406160637.541702-7-dmitry.osipenko@collabora.com>
On 4/6/23 19:06, Dmitry Osipenko wrote:
> Change locking policy of mmap() callback, making exporters responsible
> for handling dma-buf reservation locking. Previous locking policy stated
> that dma-buf is locked for both importers and exporters by the dma-buf
> core, which caused a deadlock problem for DRM drivers in a case of
> self-imported dma-bufs which required to take the lock from the DRM
> exporter side.
>
> Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com>
> Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> ---
> drivers/dma-buf/dma-buf.c | 17 +++--------------
> 1 file changed, 3 insertions(+), 14 deletions(-)
Christian, may I add yours ack to this patch?
--
Best regards,
Dmitry
next prev parent reply other threads:[~2023-05-01 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 16:06 [PATCH v2 0/7] Move dma-buf mmap() reservation locking down to exporters Dmitry Osipenko
2023-04-06 16:06 ` [PATCH v2 1/7] media: videobuf2: Don't assert held reservation lock for dma-buf mmapping Dmitry Osipenko
2023-04-12 14:39 ` Hans Verkuil
2023-04-06 16:06 ` [PATCH v2 2/7] dma-buf/heaps: " Dmitry Osipenko
2023-04-06 16:06 ` [PATCH v2 3/7] udmabuf: " Dmitry Osipenko
2023-04-06 16:06 ` [PATCH v2 4/7] fastrpc: " Dmitry Osipenko
2023-04-06 16:06 ` [PATCH v2 5/7] drm: " Dmitry Osipenko
2023-04-06 16:06 ` [PATCH v2 6/7] dma-buf: Change locking policy for mmap() Dmitry Osipenko
2023-05-01 15:42 ` Dmitry Osipenko [this message]
2023-04-06 16:06 ` [PATCH v2 7/7] drm/shmem-helper: Switch to reservation lock Dmitry Osipenko
2023-05-12 14:54 ` (subset) [PATCH v2 0/7] Move dma-buf mmap() reservation locking down to exporters Srinivas Kandagatla
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=14d7ed85-7ab6-04d9-1958-d5ceae2a79f8@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=Brian.Starkey@arm.com \
--cc=amahesh@qti.qualcomm.com \
--cc=arnd@arndb.de \
--cc=benjamin.gaignard@collabora.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jstultz@google.com \
--cc=kernel@collabora.com \
--cc=kraxel@redhat.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lmark@codeaurora.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=sumit.semwal@linaro.org \
--cc=tfiga@chromium.org \
--cc=thierry.reding@gmail.com \
--cc=tomba@kernel.org \
--cc=tzimmermann@suse.de \
/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