public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Paulo Zanoni <paulo.r.zanoni@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Jason Wessel <jason.wessel@windriver.com>
Subject: Re: [PATCH 12/13] drm/i915: remove in_dbg_master check from intel_fbc.c
Date: Wed, 4 Nov 2015 12:13:51 -0800	[thread overview]
Message-ID: <563A66FF.6090101@virtuousgeek.org> (raw)
In-Reply-To: <1446664257-32012-13-git-send-email-paulo.r.zanoni@intel.com>

On 11/04/2015 11:10 AM, Paulo Zanoni wrote:
> From our maintainer Daniel Vetter a few days ago:
>   "Oh dear this is dead code. kdbg uses the fbcon, which always uses
>   untiled, which means fbc will never be enabled. Also we have 0 users
>   and 0 test coverage for kdbg on top of i915 (Jesse implemented it
>   for fun years back). Imo just remove all this code."
> 
> Adding to what Daniel said: for kgdboc's KMS support,
> intel_pipe_set_base_atomic() already manually disables FBC, so we
> won't do the in_dbg_master() check there. This is essentially a revert
> of:
> 
> commit c924b934d0cd14a4559611da91f28f59acebe32a
> Author: Jason Wessel <jason.wessel@windriver.com>
> Date:   Thu Aug 5 09:22:32 2010 -0500
>     i915: when kgdb is active display compression should be off
> 
> Besides, it is not clear what is the exact problem caused by FBC, and
> why other features such as PSR, DRRS, IPS and RPM are not also
> checking for in_dbg_master(). IMHO we should either remove the code as
> suggested by Daniel or we add some nice comments explaining why is FBC
> so special.
> 
> v2: Rebase due to new patch order.
> 
> Cc: Jason Wessel <jason.wessel@windriver.com>
> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_fbc.c | 6 ------
>  1 file changed, 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_fbc.c b/drivers/gpu/drm/i915/intel_fbc.c
> index 8e806be..e496cb0 100644
> --- a/drivers/gpu/drm/i915/intel_fbc.c
> +++ b/drivers/gpu/drm/i915/intel_fbc.c
> @@ -890,12 +890,6 @@ static void __intel_fbc_update(struct drm_i915_private *dev_priv)
>  		goto out_disable;
>  	}
>  
> -	/* If the kernel debugger is active, always disable compression */
> -	if (in_dbg_master()) {
> -		set_no_fbc_reason(dev_priv, "Kernel debugger is active");
> -		goto out_disable;
> -	}
> -
>  	/* WaFbcExceedCdClockThreshold:hsw,bdw */
>  	if ((IS_HASWELL(dev_priv) || IS_BROADWELL(dev_priv)) &&
>  	    ilk_pipe_pixel_rate(crtc->config) >=
> 

Yeah looks fine.  I haven't had any bug reports from the kdboc work, so
I guess that means no one is using it. :)

Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-11-04 20:13 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 19:10 [PATCH 00/13] Yet another FBC series, v3 part 1 Paulo Zanoni
2015-11-04 19:10 ` [PATCH 01/13] drm/i915: rename intel_fbc_nuke to intel_fbc_recompress Paulo Zanoni
2015-11-04 19:10 ` [PATCH 02/13] drm/i915: extract fbc_on_pipe_a_only() Paulo Zanoni
2015-11-04 19:10 ` [PATCH 03/13] drm/i915: remove unnecessary check for crtc->primary->fb Paulo Zanoni
2015-11-04 19:10 ` [PATCH 04/13] drm/i915: extract crtc_is_valid() on the FBC code Paulo Zanoni
2015-11-04 19:10 ` [PATCH 05/13] drm/i915: use struct intel_crtc *crtc at __intel_fbc_update() Paulo Zanoni
2015-11-04 19:10 ` [PATCH 06/13] drm/i915: fix the __intel_fbc_update() comments Paulo Zanoni
2015-11-04 19:10 ` [PATCH 07/13] drm/i915: don't disable_fbc() if FBC is already disabled Paulo Zanoni
2015-11-05 11:29   ` Ville Syrjälä
2015-11-05 14:52     ` Maarten Lankhorst
2015-11-05 15:52       ` Ville Syrjälä
2015-11-04 19:10 ` [PATCH 08/13] drm/i915: refactor FBC deactivation at init Paulo Zanoni
2015-11-04 19:10 ` [PATCH 09/13] drm/i915: remove too-frequent FBC debug message Paulo Zanoni
2015-11-04 19:10 ` [PATCH 10/13] drm/i915: fix the CFB size check Paulo Zanoni
2015-11-10 10:22   ` Maarten Lankhorst
2015-11-10 12:20     ` Zanoni, Paulo R
2015-11-10 13:04       ` Maarten Lankhorst
2015-11-11 13:39         ` Zanoni, Paulo R
2015-11-11 14:25           ` Maarten Lankhorst
2015-11-11 14:27         ` Ville Syrjälä
2015-11-11 15:36           ` Zanoni, Paulo R
2015-11-04 19:10 ` [PATCH 11/13] drm/i915: clarify that checking the FB stride for CFB is intentional Paulo Zanoni
2015-11-04 19:10 ` [PATCH 12/13] drm/i915: remove in_dbg_master check from intel_fbc.c Paulo Zanoni
2015-11-04 20:13   ` Jesse Barnes [this message]
2015-11-04 20:19     ` Jason Wessel
2015-11-04 20:26       ` Zanoni, Paulo R
2015-11-04 20:32         ` Jesse Barnes
2015-11-04 19:10 ` [PATCH 13/13] drm/i915: remove newline from a no_fbc_reason message Paulo Zanoni
2015-11-13 15:49 ` [PATCH 00/13] Yet another FBC series, v3 part 1 Daniel Stone
2015-11-13 16:36   ` Zanoni, Paulo R
2015-11-13 16:58     ` Daniel Stone

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=563A66FF.6090101@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jason.wessel@windriver.com \
    --cc=paulo.r.zanoni@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