public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ramalingam C <ramalingam.c@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	intel-gfx@lists.freedesktop.org, daniel.vetter@ffwll.ch,
	rodrigo.vivi@intel.com, paulo.r.zanoni@intel.com
Subject: Re: [PATCH 2/2] drm/i915: frontbuffer invalidate at flip schedule
Date: Thu, 11 Jun 2015 16:27:49 +0530	[thread overview]
Message-ID: <557969AD.6080307@intel.com> (raw)
In-Reply-To: <20150611095610.GC28462@nuc-i3427.alporthouse.com>

True.

Chris and Vivi,

I am trying to understand the PSR exit and entry along with SFU 
requirement here.
AFAIK in existing code also
         on rendering start fb_obj_invalidate is calling the 
psr_invalidate(psr_exit)
         on flip prepare single frame update is done
         on flip complete frontbuffer_invalidate is calling 
psr_flush(psr_reenable)
         on rendering complete fb_obj_flush is calling the 
psr_flush(psr_reenable)

On Every rendering start if we exit the PSR, then there is no advantage 
of setting SFU at flip prepare.
Please correct me if I am wrong.

On Thursday 11 June 2015 03:26 PM, Chris Wilson wrote:
> On Thu, Jun 11, 2015 at 03:08:35PM +0530, Ramalingam C wrote:
>> After scheduling a flip for obj, frontbuffer should be invalidated.
>> Hence intel_frontbuffer_invalidate is invoked at flip preparation.
>>
>> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> References: https://bugs.freedesktop.org/show_bug.cgi?id=90418
>> ---
>>   drivers/gpu/drm/i915/intel_frontbuffer.c |    1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_frontbuffer.c b/drivers/gpu/drm/i915/intel_frontbuffer.c
>> index 4cea589..07147a7 100644
>> --- a/drivers/gpu/drm/i915/intel_frontbuffer.c
>> +++ b/drivers/gpu/drm/i915/intel_frontbuffer.c
>> @@ -268,6 +268,7 @@ void intel_frontbuffer_flip_prepare(struct drm_device *dev,
>>   	dev_priv->fb_tracking.busy_bits &= ~frontbuffer_bits;
>>   	mutex_unlock(&dev_priv->fb_tracking.lock);
>>   
>> +	intel_frontbuffer_invalidate(dev, NULL, ORIGIN_FLIP, frontbuffer_bits);
>>   	intel_psr_single_frame_update(dev);
> This then has the side effect of calling psr_invalidate (psr_exit)
> followed by the single-shot psr update, which doesn't seem desirable.
> -Chris
>

-- 
Thanks,
--Ram

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-06-11 11:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 20:38 [PATCH] drm/i915: drrs_invalidate at flip schedule Ramalingam C
2015-05-15 11:58 ` Chris Wilson
2015-05-15 13:24   ` Ramalingam C
2015-05-15 13:56     ` Chris Wilson
2015-05-18  2:49 ` shuang.he
2015-05-18  8:20 ` Daniel Vetter
2015-06-11  9:27   ` Ramalingam C
2015-06-15  9:52     ` Daniel Vetter
2015-06-15 15:15       ` Ramalingam C
2015-06-15 15:20         ` [PATCH] drm/i915: Restarting the Idleness DRRS in drrs_flush Ramalingam C
2015-06-15 15:46           ` Daniel Vetter
2015-06-11  9:38   ` [PATCH 1/2] drm/i915: fb_obj invalidate is divided into two functions Ramalingam C
2015-06-11  9:38     ` [PATCH 2/2] drm/i915: frontbuffer invalidate at flip schedule Ramalingam C
2015-06-11  9:56       ` Chris Wilson
2015-06-11 10:57         ` Ramalingam C [this message]
2015-06-14 20:59       ` shuang.he

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=557969AD.6080307@intel.com \
    --to=ramalingam.c@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulo.r.zanoni@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox