All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
	kernel test robot <lkp@intel.com>,
	"Dan Carpenter" <dan.carpenter@linaro.org>,
	Vinay Belgaumkar <vinay.belgaumkar@intel.com>,
	John Harrison <John.C.Harrison@intel.com>
Subject: Re: [PATCH] drm/i915/guc: Remove bogus null check
Date: Thu, 28 Mar 2024 21:39:17 -0400	[thread overview]
Message-ID: <ZgYbxYoSChiVRDM2@intel.com> (raw)
In-Reply-To: <ZgXkI8tw91z_2RYL@ashyti-mobl2.lan>

On Thu, Mar 28, 2024 at 10:41:55PM +0100, Andi Shyti wrote:
> Hi Rodrigo,
> 
> On Thu, Mar 28, 2024 at 05:31:07PM -0400, Rodrigo Vivi wrote:
> > This null check is bogus because we are already using 'ce' stuff
> > in many places before this function is called.
> > 
> > Having this here is useless and confuses static analyzer tools
> > that can see:
> > 
> > struct intel_engine_cs *engine = ce->engine;
> > 
> > before this check, in the same function.
> > 
> > Fixes: cec82816d0d0 ("drm/i915/guc: Use context hints for GT frequency")
> 
> there is no need to have the Fixes tag here.

why not? I imagine distros that have this commit cec82816d0d0 and use
static analyzers would also want this patch ported to silent those, no?!

> 
> > Reported-by: kernel test robot <lkp@intel.com>
> > Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> > Closes: https://lore.kernel.org/r/202403101225.7AheJhZJ-lkp@intel.com/
> > Cc: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
> > Cc: John Harrison <John.C.Harrison@Intel.com>
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > ---
> >  drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> > index 01d0ec1b30f2..24a82616f844 100644
> > --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> > +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> > @@ -2677,7 +2677,7 @@ static int guc_context_policy_init_v70(struct intel_context *ce, bool loop)
> >  	execution_quantum = engine->props.timeslice_duration_ms * 1000;
> >  	preemption_timeout = engine->props.preempt_timeout_ms * 1000;
> >  
> > -	if (ce && (ce->flags & BIT(CONTEXT_LOW_LATENCY)))
> > +	if (ce->flags & BIT(CONTEXT_LOW_LATENCY))
> 
> We could keep the check but make it earlier.

yes, that's another alternative.


-struct intel_engine_cs *engine = ce->engine;
+struct intel_engine_cs *engine;

if (!ce)
   return;

engine = ce->engine.

But looking to the 2 places where this function is getting called,
we already have ce->something used.

I can make the change to be like that if you believe that there's
a possibility in the future that we change that, just to be on
the safe side.

or anything else I might be missing?

Thanks for looking into this,
Rodrigo.

> 
> Thanks,
> Andi
> 
> >  		slpc_ctx_freq_req |= SLPC_CTX_FREQ_REQ_IS_COMPUTE;
> >  
> >  	__guc_context_policy_start_klv(&policy, ce->guc_id.id);
> > -- 
> > 2.44.0

  reply	other threads:[~2024-03-29  1:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 21:31 [PATCH] drm/i915/guc: Remove bogus null check Rodrigo Vivi
2024-03-28 21:41 ` Andi Shyti
2024-03-29  1:39   ` Rodrigo Vivi [this message]
2024-03-29  7:09     ` Andi Shyti
2024-03-29 16:38       ` Dan Carpenter
2024-04-03 18:46         ` Rodrigo Vivi
2024-03-29  6:00 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2024-03-29  6:14 ` ✓ Fi.CI.BAT: success " Patchwork
2024-03-30  5:35 ` ✗ Fi.CI.IGT: failure " 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=ZgYbxYoSChiVRDM2@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=John.C.Harrison@intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=dan.carpenter@linaro.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lkp@intel.com \
    --cc=vinay.belgaumkar@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.