Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tursulin@ursulin.net>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
	intel-xe@lists.freedesktop.org
Cc: Matt Roper <matthew.d.roper@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Francois Dugast <francois.dugast@intel.com>,
	Maarten Lankhorst <dev@lankhorst.se>
Subject: Re: [PATCH 0/7] Cleanup error handling on probe
Date: Tue, 4 Feb 2025 08:58:37 +0000	[thread overview]
Message-ID: <37e94776-ea74-4fb7-ae50-ab999324df7f@ursulin.net> (raw)
In-Reply-To: <20250131223140.4144292-1-lucas.demarchi@intel.com>


On 31/01/2025 22:31, Lucas De Marchi wrote:
> Mixing style with goto and devm_add_action_or_reset() is very confusing
> and error prone. Clean that up. The only missing one is one of the
> display calls, but that can be done in parallel to the review of these
> first patches.
> 
> This received limited load/unload tests on LNL and may very well not be
> 100%.

Is this series hinting you are looking into making heavier refactorings 
in the init code? Triggered by me recently discovering GT-per-engine 
workarounds are not working?

Regards,

Tvrtko

> Lucas De Marchi (7):
>    drm/xe: Fix xe_display_fini() calls
>    drm/xe: Fix error handling in xe_irq_install()
>    drm/xe: Fix xe_tile_init_noalloc() error propagation
>    drm/xe: Stop ignoring errors from xe_ttm_stolen_mgr_init()
>    drm/xe: Cleanup unwind of gt initialization
>    drm/xe: Cleanup extra calls to  xe_hw_fence_irq_finish()
>    drm/xe: Move oa fini to xe_oa
> 
>   drivers/gpu/drm/xe/display/xe_display.c | 22 +++++-----
>   drivers/gpu/drm/xe/display/xe_display.h |  2 -
>   drivers/gpu/drm/xe/xe_device.c          | 53 ++++++++-----------------
>   drivers/gpu/drm/xe/xe_gt.c              | 52 ++++++++++--------------
>   drivers/gpu/drm/xe/xe_gt.h              |  1 -
>   drivers/gpu/drm/xe/xe_irq.c             | 14 +------
>   drivers/gpu/drm/xe/xe_oa.c              | 48 +++++++++++-----------
>   drivers/gpu/drm/xe/xe_oa.h              |  1 -
>   drivers/gpu/drm/xe/xe_tile.c            |  4 +-
>   drivers/gpu/drm/xe/xe_ttm_stolen_mgr.c  | 17 ++++----
>   drivers/gpu/drm/xe/xe_ttm_stolen_mgr.h  |  2 +-
>   11 files changed, 86 insertions(+), 130 deletions(-)
> 

  parent reply	other threads:[~2025-02-04  8:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-31 22:31 [PATCH 0/7] Cleanup error handling on probe Lucas De Marchi
2025-01-31 22:31 ` [PATCH 1/7] drm/xe: Fix xe_display_fini() calls Lucas De Marchi
2025-02-03 20:32   ` Rodrigo Vivi
2025-01-31 22:31 ` [PATCH 2/7] drm/xe: Fix error handling in xe_irq_install() Lucas De Marchi
2025-02-03 20:36   ` Rodrigo Vivi
2025-01-31 22:31 ` [PATCH 3/7] drm/xe: Fix xe_tile_init_noalloc() error propagation Lucas De Marchi
2025-02-03 14:21   ` Francois Dugast
2025-01-31 22:31 ` [PATCH 4/7] drm/xe: Stop ignoring errors from xe_ttm_stolen_mgr_init() Lucas De Marchi
2025-02-03 14:10   ` Francois Dugast
2025-01-31 22:31 ` [PATCH 5/7] drm/xe: Cleanup unwind of gt initialization Lucas De Marchi
2025-02-01  6:24   ` Raag Jadav
2025-02-01 15:55     ` Lucas De Marchi
2025-02-02  8:09       ` Raag Jadav
2025-01-31 22:31 ` [PATCH 6/7] drm/xe: Cleanup extra calls to xe_hw_fence_irq_finish() Lucas De Marchi
2025-02-03 21:46   ` Rodrigo Vivi
2025-01-31 22:31 ` [PATCH 7/7] drm/xe: Move oa fini to xe_oa Lucas De Marchi
2025-01-31 22:37 ` ✓ CI.Patch_applied: success for Cleanup error handling on probe Patchwork
2025-01-31 22:37 ` ✓ CI.checkpatch: " Patchwork
2025-01-31 22:38 ` ✓ CI.KUnit: " Patchwork
2025-01-31 22:55 ` ✓ CI.Build: " Patchwork
2025-01-31 22:57 ` ✓ CI.Hooks: " Patchwork
2025-01-31 22:59 ` ✓ CI.checksparse: " Patchwork
2025-01-31 23:32 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-02-01  8:05 ` ✗ Xe.CI.Full: " Patchwork
2025-02-03 18:39 ` [PATCH 0/7] " Lucas De Marchi
2025-02-04  8:58 ` Tvrtko Ursulin [this message]
2025-02-04 14:50   ` Lucas De Marchi
2025-02-04 18:10     ` Tvrtko Ursulin
2025-02-04 22:42       ` Rodrigo Vivi

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=37e94776-ea74-4fb7-ae50-ab999324df7f@ursulin.net \
    --to=tursulin@ursulin.net \
    --cc=dev@lankhorst.se \
    --cc=francois.dugast@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=rodrigo.vivi@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