From: "Das, Nirmoy" <nirmoy.das@intel.com>
To: Maxime Ripard <maxime@cerno.tech>, <intel-gfx@lists.freedesktop.org>
Cc: Chris Wilson <chris.p.wilson@intel.com>,
Daniel Vetter <daniel@ffwll.ch>,
Maxime Ripard <mripard@kernel.org>,
dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/drm_vma_manager: Add drm_vma_node_allow_once()
Date: Thu, 19 Jan 2023 14:27:34 +0100 [thread overview]
Message-ID: <80953bac-073e-0750-0573-27d886e3c163@intel.com> (raw)
In-Reply-To: <167413471736.3247301.2506243938133853546.b4-ty@cerno.tech>
On 1/19/2023 2:25 PM, Maxime Ripard wrote:
> On Tue, 17 Jan 2023 18:52:35 +0100, Nirmoy Das wrote:
>> Currently there is no easy way for a drm driver to safely check and allow
>> drm_vma_offset_node for a drm file just once. Allow drm drivers to call
>> non-refcounted version of drm_vma_node_allow() so that a driver doesn't
>> need to keep track of each drm_vma_node_allow() to call subsequent
>> drm_vma_node_revoke() to prevent memory leak.
>>
>> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> Cc: Maxime Ripard <mripard@kernel.org>
>> Cc: Thomas Zimmermann <tzimmermann@suse.de>
>> Cc: David Airlie <airlied@gmail.com>
>> Cc: Daniel Vetter <daniel@ffwll.ch>
>> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
>> Cc: Andi Shyti <andi.shyti@linux.intel.com>
>>
>> [...]
> Applied to drm/drm-misc (drm-misc-fixes).
Thanks Maxime!
>
> Thanks!
> Maxime
prev parent reply other threads:[~2023-01-19 13:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 17:52 [Intel-gfx] [PATCH 1/2] drm/drm_vma_manager: Add drm_vma_node_allow_once() Nirmoy Das
2023-01-17 17:52 ` [Intel-gfx] [PATCH 2/2] drm/i915: Fix a memory leak with reused mmap_offset Nirmoy Das
2023-01-18 9:19 ` Tvrtko Ursulin
2023-01-18 9:27 ` Das, Nirmoy
2023-01-18 9:40 ` Andi Shyti
2023-01-18 10:26 ` Mirsad Todorovac
2023-01-18 10:39 ` Das, Nirmoy
2023-01-18 10:53 ` Mirsad Todorovac
2023-01-18 22:27 ` Mirsad Goran Todorovac
2023-01-17 21:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/drm_vma_manager: Add drm_vma_node_allow_once() Patchwork
2023-01-18 9:22 ` [Intel-gfx] [PATCH 1/2] " Tvrtko Ursulin
2023-01-18 9:38 ` Andi Shyti
2023-01-18 9:45 ` Das, Nirmoy
2023-01-18 11:07 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] " Patchwork
2023-01-18 13:19 ` [Intel-gfx] [PATCH 1/2] " Tvrtko Ursulin
2023-01-18 13:34 ` Tvrtko Ursulin
2023-01-19 13:25 ` Maxime Ripard
2023-01-19 13:27 ` Das, Nirmoy [this message]
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=80953bac-073e-0750-0573-27d886e3c163@intel.com \
--to=nirmoy.das@intel.com \
--cc=airlied@gmail.com \
--cc=chris.p.wilson@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maxime@cerno.tech \
--cc=mripard@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