public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Mun, Gwan-gyeong" <gwan-gyeong.mun@intel.com>
To: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Souza, Jose" <jose.souza@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/tgl/psr: Fix glitches when doing frontbuffer modifications
Date: Thu, 22 Oct 2020 12:48:57 +0000	[thread overview]
Message-ID: <b1e9804bc410c881a97045b790cfa200a0080dc8.camel@intel.com> (raw)
In-Reply-To: <c0c641e349c0078a6bead232b9f94c72f7d7aa4f.camel@intel.com>

On Thu, 2020-10-22 at 12:43 +0000, Mun, Gwan-gyeong wrote:
> 1. While testing the problematic scenario, it has not always shown
> the
> IOMMU DAMR related below errors on the drm-tip. 
>    (sometimes the error messages raised, but some times it has not
> happened on the same kernel and scenario.
>   
> DMAR: DRHD: handling fault status reg 2
> DMAR: [DMA Read] Request device [00:02.0] PASID 0xffffffff fault addr
> 0xfc001000 [fault reason 06] PTE Read access is not set
> DMAR: DRHD: handling fault status reg 3
> DMAR: [DMA Read] Request device [00:02.0] PASID 0xffffffff fault addr
> 0xfc000000 [fault reason 06] PTE Read access is not set
> 
> 2  After applying this patch the screen glitch issues have been
> remarkably alleviated.
>   - Eventhough there infrequently showed the screen glitch issues.
>   - But I agree to apply this patch as a workaround by adding the
> explanation below.
>  
> 3. The dc state and PSR enable/disable scenarios has been changed by
> this patch.
>       
> (1)Before applying patch
>   enable psr 
>     -> (front buffer updates) 
>         -> intel_psr_flush 
>                   ^   -> psr_force_hw_tracking_exit()
>                   |                   : write CURSURFLIVE 
>                   |                          |
>                   |  (front buffer updates)  |
>                   +--------------------------+
> 
>     PSR enabled -------------------------------------- -->
>    ( DC state controlled by DMC firmware)
>                                    
> 
>  (2) After applying patch
>   enable psr 
>    ^  -> (front buffer updates) 
>    |       -> intel_psr_flush
>    |          -> psr_force_hw_tracking_exit()
>    |               : call intel_psr_exit()
>    |                                 -> disable psr
>    |                                         |
>    |                                         |
>    +-----------------------------------------+
> 
> PSR enabled ---------------------------> PSR disabled
>   ^                                          |
>   |                                          |
>   +------------------------------------------+
>    ( DC state controlled by DMC firmware)
> 
> the repeating of enabling and disabling of PSR by the rapid screen
> updates prevents entering of low power dc states.
> Infereing from this scenario, it indirectly touches DC state and it
> alleviates the issue.
> 
with the previous comments,
Tested-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
Reviewed-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
> 
> On Fri, 2020-10-02 at 16:16 -0700, José Roberto de Souza wrote:
> > Writes to CURSURFLIVE in TGL are causing IOMMU errors and visual
> > glitches that are often reproduced when executing CPU intensive
> > workloads while a eDP 4K panel is attached.
> > 
> > Manually exiting PSR causes the frontbuffer to be updated without
> > glitches and the IOMMU errors are also gone but this comes at the
> > cost
> > of less time with PSR active.
> > 
> > So using this workaround until this issue is root caused and a
> > better
> > fix is found.
> > 
> > The current code is already ready to enable PSR after this exit if
> > there is not other frontbuffer modifications.
> > 
> > Adding a new if block in psr_force_hw_tracking_exit() instead of
> > reuse
> > the else/gen8- block because the plan is to revert this workaround
> > as soon as a better solution is found.
> > 
> > Cc: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > ---
> >  drivers/gpu/drm/i915/display/intel_psr.c | 16 +++++++++++++++-
> >  1 file changed, 15 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/intel_psr.c
> > b/drivers/gpu/drm/i915/display/intel_psr.c
> > index 8a9d0bdde1bf..8630121dbbbe 100644
> > --- a/drivers/gpu/drm/i915/display/intel_psr.c
> > +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> > @@ -1152,7 +1152,21 @@ void intel_psr_disable(struct intel_dp
> > *intel_dp,
> >  
> >  static void psr_force_hw_tracking_exit(struct drm_i915_private
> > *dev_priv)
> >  {
> > -	if (INTEL_GEN(dev_priv) >= 9)
> > +	if (IS_TIGERLAKE(dev_priv))
> > +		/*
> > +		 * Writes to CURSURFLIVE in TGL are causing IOMMU
> > errors and
> > +		 * visual glitches that are often reproduced when
> > executing
> > +		 * CPU intensive workloads while a eDP 4K panel is
> > attached.
> > +		 *
> > +		 * Manually exiting PSR causes the frontbuffer to be
> > updated
> > +		 * without glitches and the IOMMU errors are also gone
> > but
> > +		 * this comes at the cost of less time with PSR active.
> > +		 *
> > +		 * So using this workaround until this issue is root
> > caused
> > +		 * and a better fix is found.
> > +		 */
> > +		intel_psr_exit(dev_priv);
> > +	else if (INTEL_GEN(dev_priv) >= 9)
> >  		/*
> >  		 * Display WA #0884: skl+
> >  		 * This documented WA for bxt can be safely applied
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-10-22 12:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 23:16 [Intel-gfx] [PATCH] drm/i915/tgl/psr: Fix glitches when doing frontbuffer modifications José Roberto de Souza
2020-10-02 23:46 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-10-03  1:26 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-10-05 18:55   ` Souza, Jose
2020-10-05 19:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/tgl/psr: Fix glitches when doing frontbuffer modifications (rev2) Patchwork
2020-10-05 21:48 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-10-23 21:31   ` Souza, Jose
2020-10-12 18:12 ` [Intel-gfx] [PATCH] drm/i915/tgl/psr: Fix glitches when doing frontbuffer modifications Mun, Gwan-gyeong
2020-10-12 18:15   ` Souza, Jose
2020-10-12 19:04     ` Mun, Gwan-gyeong
2020-10-22 12:43 ` Mun, Gwan-gyeong
2020-10-22 12:48   ` Mun, Gwan-gyeong [this message]
2020-10-23 21:27     ` Souza, Jose

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=b1e9804bc410c881a97045b790cfa200a0080dc8.camel@intel.com \
    --to=gwan-gyeong.mun@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jose.souza@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