From: "Ruhl, Michael J" <michael.j.ruhl@intel.com> To: "Christian König" <ckoenig.leichtzumerken@gmail.com>, "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org> Cc: "matthew.william.auld@gmail.com" <matthew.william.auld@gmail.com>, "Christian König" <christian.koenig@amd.com>, "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org> Subject: RE: [PATCH 04/11] drm/ttm: move default BO destructor into VMWGFX Date: Thu, 19 May 2022 13:36:45 +0000 [thread overview] Message-ID: <DM5PR11MB1324DCAE7CD6B1F16920B5B5C1D09@DM5PR11MB1324.namprd11.prod.outlook.com> (raw) In-Reply-To: <20220519095508.115203-5-christian.koenig@amd.com> >-----Original Message----- >From: dri-devel <dri-devel-bounces@lists.freedesktop.org> On Behalf Of >Christian König >Sent: Thursday, May 19, 2022 5:55 AM >To: intel-gfx@lists.freedesktop.org >Cc: matthew.william.auld@gmail.com; Christian König ><christian.koenig@amd.com>; dri-devel@lists.freedesktop.org >Subject: [PATCH 04/11] drm/ttm: move default BO destructor into VMWGFX > >It's the only driver using this. > >Signed-off-by: Christian König <christian.koenig@amd.com> >--- > drivers/gpu/drm/vmwgfx/vmwgfx_bo.c | 3 +++ > 1 file changed, 3 insertions(+) > >diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_bo.c >b/drivers/gpu/drm/vmwgfx/vmwgfx_bo.c >index 85a66014c2b6..c4f376d5e1d0 100644 >--- a/drivers/gpu/drm/vmwgfx/vmwgfx_bo.c >+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_bo.c >@@ -462,6 +462,9 @@ int vmw_bo_create(struct vmw_private *vmw, > return -ENOMEM; > } > >+ if (!bo_free) >+ bo_free = vmw_bo_default_destroy; >+ vmw_bo_init has a WARN_ON if this is NULL. Also, all of the callers use vmw_bo_bo_free() or vmw_gem_destroy(). Both of those unmap, release and then free the object. It doesn't look like vmw_bo_default_destroy does this work. Is this the right "default" path? Or should the WARN_ON be used to check for this? M > ret = vmw_bo_init(vmw, *p_bo, size, > placement, interruptible, pin, > bo_free); >-- >2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: "Ruhl, Michael J" <michael.j.ruhl@intel.com> To: "Christian König" <ckoenig.leichtzumerken@gmail.com>, "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org> Cc: "Christian König" <christian.koenig@amd.com>, "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org> Subject: Re: [Intel-gfx] [PATCH 04/11] drm/ttm: move default BO destructor into VMWGFX Date: Thu, 19 May 2022 13:36:45 +0000 [thread overview] Message-ID: <DM5PR11MB1324DCAE7CD6B1F16920B5B5C1D09@DM5PR11MB1324.namprd11.prod.outlook.com> (raw) In-Reply-To: <20220519095508.115203-5-christian.koenig@amd.com> >-----Original Message----- >From: dri-devel <dri-devel-bounces@lists.freedesktop.org> On Behalf Of >Christian König >Sent: Thursday, May 19, 2022 5:55 AM >To: intel-gfx@lists.freedesktop.org >Cc: matthew.william.auld@gmail.com; Christian König ><christian.koenig@amd.com>; dri-devel@lists.freedesktop.org >Subject: [PATCH 04/11] drm/ttm: move default BO destructor into VMWGFX > >It's the only driver using this. > >Signed-off-by: Christian König <christian.koenig@amd.com> >--- > drivers/gpu/drm/vmwgfx/vmwgfx_bo.c | 3 +++ > 1 file changed, 3 insertions(+) > >diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_bo.c >b/drivers/gpu/drm/vmwgfx/vmwgfx_bo.c >index 85a66014c2b6..c4f376d5e1d0 100644 >--- a/drivers/gpu/drm/vmwgfx/vmwgfx_bo.c >+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_bo.c >@@ -462,6 +462,9 @@ int vmw_bo_create(struct vmw_private *vmw, > return -ENOMEM; > } > >+ if (!bo_free) >+ bo_free = vmw_bo_default_destroy; >+ vmw_bo_init has a WARN_ON if this is NULL. Also, all of the callers use vmw_bo_bo_free() or vmw_gem_destroy(). Both of those unmap, release and then free the object. It doesn't look like vmw_bo_default_destroy does this work. Is this the right "default" path? Or should the WARN_ON be used to check for this? M > ret = vmw_bo_init(vmw, *p_bo, size, > placement, interruptible, pin, > bo_free); >-- >2.25.1
next prev parent reply other threads:[~2022-05-19 13:36 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-19 9:54 Christian König 2022-05-19 9:54 ` [PATCH 01/11] drm/radeon: switch over to ttm_bo_init_reserved Christian König 2022-05-19 12:54 ` Ruhl, Michael J 2022-05-19 12:54 ` [Intel-gfx] " Ruhl, Michael J 2022-05-19 13:09 ` Christian König 2022-05-19 13:09 ` [Intel-gfx] " Christian König 2022-05-19 9:54 ` [PATCH 02/11] drm/nouveau: " Christian König 2022-05-19 13:19 ` Ruhl, Michael J 2022-05-19 13:19 ` [Intel-gfx] " Ruhl, Michael J 2022-05-20 7:13 ` Christian König 2022-05-20 7:13 ` [Intel-gfx] " Christian König 2022-05-19 9:55 ` [PATCH 03/11] drm/vram-helper: " Christian König 2022-05-19 9:55 ` [PATCH 04/11] drm/ttm: move default BO destructor into VMWGFX Christian König 2022-05-19 13:36 ` Ruhl, Michael J [this message] 2022-05-19 13:36 ` [Intel-gfx] " Ruhl, Michael J 2022-05-20 7:14 ` Christian König 2022-05-20 7:14 ` [Intel-gfx] " Christian König 2022-05-19 9:55 ` [PATCH 05/11] drm/ttm: drop ttm_bo_init Christian König 2022-05-19 9:55 ` [PATCH 06/11] drm/ttm: rename and cleanup ttm_bo_init_reserved Christian König 2022-05-19 13:54 ` Ruhl, Michael J 2022-05-19 13:54 ` [Intel-gfx] " Ruhl, Michael J 2022-05-19 9:55 ` [PATCH 07/11] drm/amdgpu: audit bo->resource usage Christian König 2022-05-19 9:55 ` [PATCH 08/11] drm/nouveau: " Christian König 2022-05-19 9:55 ` [PATCH 09/11] drm/ttm: " Christian König 2022-05-19 14:15 ` Ruhl, Michael J 2022-05-19 14:15 ` [Intel-gfx] " Ruhl, Michael J 2022-05-19 9:55 ` [PATCH 10/11] drm/ttm: stop allocating dummy resources during BO creation Christian König 2022-05-20 7:02 ` [drm/ttm] 47e8c5019b: BUG:kernel_NULL_pointer_dereference,address kernel test robot 2022-05-20 7:02 ` [drm/ttm] 47e8c5019b: BUG:kernel_NULL_pointer_dereference, address kernel test robot 2022-05-20 7:02 ` [Intel-gfx] " kernel test robot 2022-05-20 7:02 ` [drm/ttm] 47e8c5019b: BUG:kernel_NULL_pointer_dereference,address kernel test robot 2022-05-19 9:55 ` [PATCH 11/11] drm/ttm: stop allocating a dummy resource for pipelined gutting Christian König 2022-05-19 10:50 ` Matthew Auld 2022-05-19 10:50 ` [Intel-gfx] (no subject) Matthew Auld 2022-05-20 7:11 ` Christian König -- strict thread matches above, loose matches on Subject: below -- 2022-05-09 13:09 Improve TTMs empty object handling Christian König 2022-05-09 13:09 ` [PATCH 04/11] drm/ttm: move default BO destructor into VMWGFX Christian König 2022-03-29 11:02 Allow ttm_buffer_object without resource Christian König 2022-03-29 11:02 ` [PATCH 04/11] drm/ttm: move default BO destructor into VMWGFX Christian König 2022-04-18 19:45 ` Zack Rusin
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=DM5PR11MB1324DCAE7CD6B1F16920B5B5C1D09@DM5PR11MB1324.namprd11.prod.outlook.com \ --to=michael.j.ruhl@intel.com \ --cc=christian.koenig@amd.com \ --cc=ckoenig.leichtzumerken@gmail.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=intel-gfx@lists.freedesktop.org \ --cc=matthew.william.auld@gmail.com \ /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: linkBe 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.