public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Increase atomic update vblank evasion time with lockdep
Date: Tue, 10 Oct 2017 11:57:18 +0300	[thread overview]
Message-ID: <20171010085718.GK10981@intel.com> (raw)
In-Reply-To: <20171010084657.25756-1-daniel.vetter@ffwll.ch>

On Tue, Oct 10, 2017 at 10:46:57AM +0200, Daniel Vetter wrote:
> All our mmio writes take forever with lockdep due to the constant
> lock acquire&dropping we do. Ville has some patches to only acquire
> the mmio spinlocks once instead for every single mmio, but those
> aren't ready yet.
> 
> As an interim solution just extend our budget slightly when lockdep is
> enabled, to avoid the rare and sporadic noise in CI.
> 
> Cc: Ville Syrjala <ville.syrjala@linux.intel.com>
> References: https://bugs.freedesktop.org/show_bug.cgi?id=103169
> References: https://bugs.freedesktop.org/show_bug.cgi?id=103124
> References: https://bugs.freedesktop.org/show_bug.cgi?id=102403
> References: https://bugs.freedesktop.org/show_bug.cgi?id=103020
> References: https://bugs.freedesktop.org/show_bug.cgi?id=103019
> References: https://bugs.freedesktop.org/show_bug.cgi?id=102723
> References: https://bugs.freedesktop.org/show_bug.cgi?id=102544
> References: https://bugs.freedesktop.org/show_bug.cgi?id=103180
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>

Acked-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

> ---
>  drivers/gpu/drm/i915/intel_sprite.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/intel_sprite.c b/drivers/gpu/drm/i915/intel_sprite.c
> index b0d6e3e28d07..65f1bffe295d 100644
> --- a/drivers/gpu/drm/i915/intel_sprite.c
> +++ b/drivers/gpu/drm/i915/intel_sprite.c
> @@ -66,7 +66,11 @@ int intel_usecs_to_scanlines(const struct drm_display_mode *adjusted_mode,
>  			    1000 * adjusted_mode->crtc_htotal);
>  }
>  
> +#if IS_ENABLED(CONFIG_PROVE_LOCKING)
> +#define VBLANK_EVASION_TIME_US 250
> +#else
>  #define VBLANK_EVASION_TIME_US 100
> +#endif
>  
>  /**
>   * intel_pipe_update_start() - start update of a set of display registers
> -- 
> 2.14.1

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-10-10  8:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10  8:46 [PATCH] drm/i915: Increase atomic update vblank evasion time with lockdep Daniel Vetter
2017-10-10  8:57 ` Ville Syrjälä [this message]
2017-10-10  9:07 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-10-10  9:18   ` [PATCH] " Daniel Vetter
2017-10-10  9:41   ` ✓ Fi.CI.BAT: success for drm/i915: Increase atomic update vblank evasion time with lockdep (rev2) Patchwork
2017-10-10 10:56   ` ✗ Fi.CI.IGT: failure " Patchwork
2017-10-10 10:05 ` ✓ Fi.CI.IGT: success for drm/i915: Increase atomic update vblank evasion time with lockdep 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=20171010085718.GK10981@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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