Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: dri-devel@lists.freedesktop.org, John Stultz <jstultz@google.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	kernel@collabora.com, Sumit Semwal <sumit.semwal@linaro.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Benjamin Gaignard <benjamin.gaignard@collabora.com>,
	linux-media@vger.kernel.org, Daniel Vetter <daniel@ffwll.ch>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-arm-msm@vger.kernel.org, intel-gfx@lists.freedesktop.org,
	linux-tegra@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Tomi Valkeinen <tomba@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, Liam Mark <lmark@codeaurora.org>,
	Tomasz Figa <tfiga@chromium.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Amol Maheshwari <amahesh@qti.qualcomm.com>
Subject: Re: [Intel-gfx] [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


  reply	other threads:[~2023-05-01 15:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 16:06 [Intel-gfx] [PATCH v2 0/7] Move dma-buf mmap() reservation locking down to exporters Dmitry Osipenko
2023-04-06 16:06 ` [Intel-gfx] [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 ` [Intel-gfx] [PATCH v2 2/7] dma-buf/heaps: " Dmitry Osipenko
2023-04-06 16:06 ` [Intel-gfx] [PATCH v2 3/7] udmabuf: " Dmitry Osipenko
2023-04-06 16:06 ` [Intel-gfx] [PATCH v2 4/7] fastrpc: " Dmitry Osipenko
2023-04-06 16:06 ` [Intel-gfx] [PATCH v2 5/7] drm: " Dmitry Osipenko
2023-04-06 16:06 ` [Intel-gfx] [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 ` [Intel-gfx] [PATCH v2 7/7] drm/shmem-helper: Switch to reservation lock Dmitry Osipenko
2023-04-06 18:11 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Move dma-buf mmap() reservation locking down to exporters (rev2) Patchwork
2023-04-06 18:28 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-05-12 14:54 ` [Intel-gfx] (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=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=gregkh@linuxfoundation.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --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=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