Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	Lucas De Marchi <lucas.demarchi@intel.com>,
	Matthew Auld <matthew.auld@intel.com>,
	"John Harrison" <John.C.Harrison@intel.com>,
	Alan Previn <alan.previn.teres.alexis@intel.com>
Subject: Re: [PATCH 0/3] uC-related drmm vs devm fixes
Date: Fri, 9 Aug 2024 23:46:02 +0000	[thread overview]
Message-ID: <ZraqOtF30QPXEwkv@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240809231237.1503796-1-daniele.ceraolospurio@intel.com>

On Fri, Aug 09, 2024 at 04:12:34PM -0700, Daniele Ceraolo Spurio wrote:
> If HW access is required for cleaning up a resource, we need to use devm
> callbacks instead of drmm ones, otherwise the HW might already be gone
> by the time the cleanup function is called.
> 
> The first patch in the series fixes the managed_bo callback, which is
> not uC-specific but it is used to clean up the uC objects. The second
> and third patch fix cleanup of BOs and exec_queues in uC code.
> 

I can confirm this is fixing the issue mentioned in the cover letter [1]
here.

Matt

[1] https://patchwork.freedesktop.org/series/137111/

> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> Cc: Matthew Auld <matthew.auld@intel.com>
> Cc: John Harrison <John.C.Harrison@Intel.com>
> Cc: Alan Previn <alan.previn.teres.alexis@intel.com>
> 
> Daniele Ceraolo Spurio (3):
>   drm/xe: use devm instead of drmm for managed bo
>   drm/xe/uc: Use managed bo for HuC and GSC objects
>   drm/xe/uc: Use devm to register cleanup that includes exec_queues
> 
>  drivers/gpu/drm/xe/xe_bo.c         |  6 ++---
>  drivers/gpu/drm/xe/xe_gsc.c        | 16 +++++--------
>  drivers/gpu/drm/xe/xe_gsc_proxy.c  | 36 +++++-------------------------
>  drivers/gpu/drm/xe/xe_guc_submit.c |  4 ++--
>  drivers/gpu/drm/xe/xe_huc.c        | 19 +++++-----------
>  5 files changed, 21 insertions(+), 60 deletions(-)
> 
> -- 
> 2.43.0
> 

  parent reply	other threads:[~2024-08-09 23:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09 23:12 [PATCH 0/3] uC-related drmm vs devm fixes Daniele Ceraolo Spurio
2024-08-09 23:12 ` [PATCH 1/3] drm/xe: use devm instead of drmm for managed bo Daniele Ceraolo Spurio
2024-08-10  4:39   ` Lucas De Marchi
2024-08-12 10:41   ` Matthew Auld
2024-08-12 16:38     ` Daniele Ceraolo Spurio
2024-08-12 18:17       ` Matthew Auld
2024-08-12 18:43         ` Daniele Ceraolo Spurio
2024-08-09 23:12 ` [PATCH 2/3] drm/xe/uc: Use managed bo for HuC and GSC objects Daniele Ceraolo Spurio
2024-08-15 20:00   ` Lucas De Marchi
2024-08-15 20:44     ` Daniele Ceraolo Spurio
2024-08-09 23:12 ` [PATCH 3/3] drm/xe/uc: Use devm to register cleanup that includes exec_queues Daniele Ceraolo Spurio
2024-08-09 23:46 ` Matthew Brost [this message]
2024-08-10  0:06 ` ✓ CI.Patch_applied: success for uC-related drmm vs devm fixes Patchwork
2024-08-10  0:06 ` ✓ CI.checkpatch: " Patchwork
2024-08-10  0:07 ` ✓ CI.KUnit: " Patchwork
2024-08-10  0:24 ` ✓ CI.Build: " Patchwork
2024-08-10  0:29 ` ✓ CI.Hooks: " Patchwork
2024-08-10  0:31 ` ✓ CI.checksparse: " Patchwork
2024-08-10  0:52 ` ✗ CI.BAT: failure " Patchwork
2024-08-10  3:44 ` ✗ CI.FULL: " Patchwork

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=ZraqOtF30QPXEwkv@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=John.C.Harrison@intel.com \
    --cc=alan.previn.teres.alexis@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.auld@intel.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: 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