From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: "Christian König" <christian.koenig@amd.com>
Cc: linaro-mm-sig@lists.linaro.org,
Gustavo Padovan <gustavo@padovan.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Tomasz Figa <tfiga@chromium.org>,
Christoph Hellwig <hch@infradead.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Ricardo Ribalda <ribalda@chromium.org>,
Sumit Semwal <sumit.semwal@linaro.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] dma-fence: allow dma fence to have their own lock
Date: Tue, 31 May 2022 11:51:42 +0900 [thread overview]
Message-ID: <YpWCvniLzJfcp684@google.com> (raw)
In-Reply-To: <7eee4274-bd69-df8d-9067-771366217804@amd.com>
On (22/05/30 16:55), Christian König wrote:
> Am 30.05.22 um 16:22 schrieb Sergey Senozhatsky:
> > [SNIP]
> > So the `lock` should have at least same lifespan as the DMA fence
> > that borrows it, which is impossible to guarantee in our case.
>
> Nope, that's not correct. The lock should have at least same lifespan as the
> context of the DMA fence.
How does one know when it's safe to release the context? DMA fence
objects are still transparently refcount-ed and "live their own lives",
how does one synchronize lifespans?
WARNING: multiple messages have this Message-ID (diff)
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: "Christian König" <christian.koenig@amd.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Sumit Semwal <sumit.semwal@linaro.org>,
Gustavo Padovan <gustavo@padovan.org>,
Tomasz Figa <tfiga@chromium.org>,
Ricardo Ribalda <ribalda@chromium.org>,
Christoph Hellwig <hch@infradead.org>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dma-fence: allow dma fence to have their own lock
Date: Tue, 31 May 2022 11:51:42 +0900 [thread overview]
Message-ID: <YpWCvniLzJfcp684@google.com> (raw)
In-Reply-To: <7eee4274-bd69-df8d-9067-771366217804@amd.com>
On (22/05/30 16:55), Christian König wrote:
> Am 30.05.22 um 16:22 schrieb Sergey Senozhatsky:
> > [SNIP]
> > So the `lock` should have at least same lifespan as the DMA fence
> > that borrows it, which is impossible to guarantee in our case.
>
> Nope, that's not correct. The lock should have at least same lifespan as the
> context of the DMA fence.
How does one know when it's safe to release the context? DMA fence
objects are still transparently refcount-ed and "live their own lives",
how does one synchronize lifespans?
next prev parent reply other threads:[~2022-05-31 2:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 14:22 [PATCH] dma-fence: allow dma fence to have their own lock Sergey Senozhatsky
2022-05-30 14:22 ` Sergey Senozhatsky
2022-05-30 14:55 ` Christian König
2022-05-30 14:55 ` Christian König
2022-05-30 15:09 ` Sergey Senozhatsky
2022-05-30 15:09 ` Sergey Senozhatsky
2022-05-30 15:45 ` Sergey Senozhatsky
2022-05-30 15:45 ` Sergey Senozhatsky
2022-06-01 13:50 ` [Linaro-mm-sig] " Christian König
2022-06-01 13:50 ` Christian König
2022-05-31 2:51 ` Sergey Senozhatsky [this message]
2022-05-31 2:51 ` Sergey Senozhatsky
2022-06-01 12:45 ` [Linaro-mm-sig] " Christian König
2022-06-01 12:45 ` Christian König
2022-06-01 13:22 ` Daniel Vetter
2022-06-01 13:22 ` Daniel Vetter
2022-06-01 13:52 ` Christian König
2022-06-01 14:27 ` Sergey Senozhatsky
2022-06-01 14:27 ` Sergey Senozhatsky
2022-06-01 14:38 ` Christian König
2022-06-01 14:38 ` Christian König
2022-06-01 14:52 ` Sergey Senozhatsky
2022-06-01 14:52 ` Sergey Senozhatsky
2022-06-01 15:06 ` Christian König
2022-06-01 15:06 ` 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=YpWCvniLzJfcp684@google.com \
--to=senozhatsky@chromium.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=hch@infradead.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=ribalda@chromium.org \
--cc=sumit.semwal@linaro.org \
--cc=tfiga@chromium.org \
/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.