All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	Lucas De Marchi <lucas.demarchi@intel.com>,
	Matthew Auld <matthew.auld@intel.com>
Subject: Re: [PATCH] drm/xe: Return immediately on tile_init failure
Date: Wed, 6 Mar 2024 16:37:29 -0500	[thread overview]
Message-ID: <ZejiGZu4LRDdZ0RL@intel.com> (raw)
In-Reply-To: <20240306205341.GA718896@mdroper-desk1.amr.corp.intel.com>

On Wed, Mar 06, 2024 at 12:53:41PM -0800, Matt Roper wrote:
> On Wed, Mar 06, 2024 at 03:31:10PM -0500, Rodrigo Vivi wrote:
> > There's no reason to proceed with applying workaround and initing
> > sysfs if we are going to abort the probe upon failure.
> > 
> > Fixes: 876611c2b756 ("drm/xe: Memory allocations are tile-based, not GT-based")
> 
> Should this actually be
> 
> Fixes: e5a845fd8fa4 ("drm/xe: Add sysfs entry for tile")
> 
> instead?  The commit you cited here was already returning immediately as
> expected, but the sysfs commit started adding additional steps in the
> middle.

that was indeed the first bad case. I replaced the fixes while
pushing the patch. Thanks for the correction.

> 
> Anyway,
> 
> Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
> 
> > Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> > Cc: Matt Roper <matthew.d.roper@intel.com>
> > Cc: Matthew Auld <matthew.auld@intel.com>
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > ---
> >  drivers/gpu/drm/xe/xe_tile.c | 5 +++--
> >  1 file changed, 3 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/xe/xe_tile.c b/drivers/gpu/drm/xe/xe_tile.c
> > index 044c20881de7..0650b2fa75ef 100644
> > --- a/drivers/gpu/drm/xe/xe_tile.c
> > +++ b/drivers/gpu/drm/xe/xe_tile.c
> > @@ -167,9 +167,10 @@ int xe_tile_init_noalloc(struct xe_tile *tile)
> >  		goto err_mem_access;
> >  
> >  	tile->mem.kernel_bb_pool = xe_sa_bo_manager_init(tile, SZ_1M, 16);
> > -	if (IS_ERR(tile->mem.kernel_bb_pool))
> > +	if (IS_ERR(tile->mem.kernel_bb_pool)) {
> >  		err = PTR_ERR(tile->mem.kernel_bb_pool);
> > -
> > +		goto err_mem_access;
> > +	}
> >  	xe_wa_apply_tile_workarounds(tile);
> >  
> >  	xe_tile_sysfs_init(tile);
> > -- 
> > 2.43.2
> > 
> 
> -- 
> Matt Roper
> Graphics Software Engineer
> Linux GPU Platform Enablement
> Intel Corporation

  reply	other threads:[~2024-03-06 21:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 20:31 [PATCH] drm/xe: Return immediately on tile_init failure Rodrigo Vivi
2024-03-06 20:36 ` ✓ CI.Patch_applied: success for " Patchwork
2024-03-06 20:36 ` ✓ CI.checkpatch: " Patchwork
2024-03-06 20:37 ` ✓ CI.KUnit: " Patchwork
2024-03-06 20:48 ` ✓ CI.Build: " Patchwork
2024-03-06 20:48 ` ✗ CI.Hooks: failure " Patchwork
2024-03-06 20:49 ` ✓ CI.checksparse: success " Patchwork
2024-03-06 20:53 ` [PATCH] " Matt Roper
2024-03-06 21:37   ` Rodrigo Vivi [this message]
2024-03-06 21:23 ` ✓ CI.BAT: success for " 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=ZejiGZu4LRDdZ0RL@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.auld@intel.com \
    --cc=matthew.d.roper@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 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.