From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Cc: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: Warn on if set frontbuffer return value is not NULL on release
Date: Thu, 28 Sep 2023 08:31:02 +0000 [thread overview]
Message-ID: <4034cb8624e959ef65b0272427a9c2df625d4004.camel@intel.com> (raw)
In-Reply-To: <87cyy2kajy.fsf@intel.com>
On Thu, 2023-09-28 at 10:43 +0300, Jani Nikula wrote:
> On Thu, 28 Sep 2023, Jouni Högander <jouni.hogander@intel.com> wrote:
> > i915_gem_object_set_frontbuffer returns set frontbuffer pointer.
> > When we
> > are releasing frontbuffer we are clearing the pointer from the
> > object. Warn
> > on if return value is not null.
> >
> > v2: Instead of ignoring do drm_WARN_ON
> >
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> >
> > Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_frontbuffer.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_frontbuffer.c
> > b/drivers/gpu/drm/i915/display/intel_frontbuffer.c
> > index d5540c739404..95319301cf2b 100644
> > --- a/drivers/gpu/drm/i915/display/intel_frontbuffer.c
> > +++ b/drivers/gpu/drm/i915/display/intel_frontbuffer.c
> > @@ -259,7 +259,8 @@ static void frontbuffer_release(struct kref
> > *ref)
> >
> > i915_ggtt_clear_scanout(obj);
> >
> > - i915_gem_object_set_frontbuffer(obj, NULL);
> > + drm_WARN_ON(&intel_bo_to_i915(obj)->drm,
> > + i915_gem_object_set_frontbuffer(obj, NULL) !=
> > NULL);
>
> I'm in the camp that says drm_WARN_ON() and friends should not
> contain
> any functional actions, and it should just be for checks. I.e. if you
> removed all the warns, things would still work, and lines that do
> stuff
> stand out and aren't hidden in WARN parameters.
>
> Like so:
>
> ret = i915_gem_object_set_frontbuffer(obj, NULL);
> drm_WARN_ON(&intel_bo_to_i915(obj)->drm, ret);
Thank you Jani for bringing up this aspect. Just sent a new version of
this patch. Please check.
BR,
Jouni Högander
>
> BR,
> Jani.
>
> > spin_unlock(&intel_bo_to_i915(obj)-
> > >display.fb_tracking.lock);
> >
> > i915_active_fini(&front->write);
>
next prev parent reply other threads:[~2023-09-28 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 6:52 [Intel-gfx] [PATCH v2] drm/i915: Warn on if set frontbuffer return value is not NULL on release Jouni Högander
2023-09-28 7:32 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-09-28 7:43 ` [Intel-gfx] [PATCH v2] " Jani Nikula
2023-09-28 8:31 ` Hogander, Jouni [this message]
2023-09-29 13:29 ` Gustavo Sousa
2023-10-02 7:08 ` Jani Nikula
2023-10-02 12:28 ` Gustavo Sousa
2023-09-28 7:46 ` [Intel-gfx] ✓ Fi.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=4034cb8624e959ef65b0272427a9c2df625d4004.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.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