All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: Missing notifications for front buffer status change(invalidate)
Date: Wed, 18 Mar 2015 10:51:58 +0100	[thread overview]
Message-ID: <20150318095158.GI31422@phenom.ffwll.local> (raw)
In-Reply-To: <55093CED.4060709@intel.com>

On Wed, Mar 18, 2015 at 02:23:01PM +0530, Ramalingam C wrote:
> cc += intel-gfx
> 
> On Wednesday 18 March 2015 02:12 PM, Ramalingam C wrote:
> >Hi,
> >
> >Is there anyway I can test the front buffer tracking?
> >
> >On latest drm-intel-nightly, I am observing that when ubuntu bootsup after
> >few secs (like ~15Secs)
> >there no call from intel_fb_obj_invalidate() to invalidate the drrs.
> >
> >But system is healthy and FBs are keep changing. But no notification to
> >DRRS for FB status change.
> >
> >I have verified this by observing the busy_frontbuffer_bits from
> >/sys/kernel/debug/dri/0/i915_drrs_status. This bit is not changing at all.
> >Hence DRRS is stuck at DRRS_LOW_RR itself.
> >
> >Is it known valid issue? Or am I doing something wrong.!?

Yeah that shouldn't happen indeed. Unfortunately we've created the
frontbuffer code for fbc/psr, and that code is still not yet enabled by
default. So testing for frontbuffer tracking is probably too thin. And we
still discover corner-cases in the frontbuffer tracking logic.

So "just" tracking down what's going and fix it. Plus perhaps we do indeed
need a DRRS testcase to exercise these corner-cases and check that the
kernel does correctly switch between low and high modes.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2015-03-18  9:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <55093A81.1050701@intel.com>
2015-03-18  8:53 ` Missing notifications for front buffer status change(invalidate) Ramalingam C
2015-03-18  9:51   ` Daniel Vetter [this message]

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=20150318095158.GI31422@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ramalingam.c@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.