From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915/fbc: replace GEM_BUG_ON() to drm_WARN_ON()
Date: Thu, 14 Sep 2023 08:40:40 -0400 [thread overview]
Message-ID: <ZQL/SBEn8sc4K7hf@intel.com> (raw)
In-Reply-To: <a7d53a403822b43c7d78689a10480b47ccc0534d.1694684044.git.jani.nikula@intel.com>
On Thu, Sep 14, 2023 at 12:34:57PM +0300, Jani Nikula wrote:
> Avoid using GEM_BUG_ON() in display code.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_fbc.c | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_fbc.c b/drivers/gpu/drm/i915/display/intel_fbc.c
> index 817e5784660b..1cb9eec29640 100644
> --- a/drivers/gpu/drm/i915/display/intel_fbc.c
> +++ b/drivers/gpu/drm/i915/display/intel_fbc.c
> @@ -333,12 +333,14 @@ static void i8xx_fbc_program_cfb(struct intel_fbc *fbc)
> {
> struct drm_i915_private *i915 = fbc->i915;
>
> - GEM_BUG_ON(range_overflows_end_t(u64, i915_gem_stolen_area_address(i915),
> - i915_gem_stolen_node_offset(&fbc->compressed_fb),
> - U32_MAX));
> - GEM_BUG_ON(range_overflows_end_t(u64, i915_gem_stolen_area_address(i915),
> - i915_gem_stolen_node_offset(&fbc->compressed_llb),
> - U32_MAX));
> + drm_WARN_ON(&i915->drm,
> + range_overflows_end_t(u64, i915_gem_stolen_area_address(i915),
> + i915_gem_stolen_node_offset(&fbc->compressed_fb),
> + U32_MAX));
> + drm_WARN_ON(&i915->drm,
> + range_overflows_end_t(u64, i915_gem_stolen_area_address(i915),
> + i915_gem_stolen_node_offset(&fbc->compressed_llb),
> + U32_MAX));
> intel_de_write(i915, FBC_CFB_BASE,
> i915_gem_stolen_node_address(i915, &fbc->compressed_fb));
> intel_de_write(i915, FBC_LL_BASE,
> --
> 2.39.2
>
next prev parent reply other threads:[~2023-09-14 12:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 9:34 [Intel-gfx] [PATCH 0/3] drm/i915/display: remove last uses of GEM_BUG_ON/GEM_WARN_ON Jani Nikula
2023-09-14 9:34 ` [Intel-gfx] [PATCH 1/3] drm/i915/fbc: replace GEM_BUG_ON() to drm_WARN_ON() Jani Nikula
2023-09-14 12:40 ` Rodrigo Vivi [this message]
2023-09-15 15:28 ` Jani Nikula
2023-09-14 9:34 ` [Intel-gfx] [PATCH 2/3] drm/i915/fb: replace GEM_WARN_ON() with drm_WARN_ON() Jani Nikula
2023-09-14 12:41 ` Rodrigo Vivi
2023-09-14 9:34 ` [Intel-gfx] [PATCH 3/3] drm/i915/dpt: replace GEM_BUG_ON() " Jani Nikula
2023-09-14 12:41 ` Rodrigo Vivi
2023-09-14 16:48 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/display: remove last uses of GEM_BUG_ON/GEM_WARN_ON Patchwork
2023-09-14 17:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-09-14 21:44 ` [Intel-gfx] ✗ 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=ZQL/SBEn8sc4K7hf@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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