All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Click the ACTHD three times to go home
Date: Mon, 27 Mar 2017 17:00:49 +0300	[thread overview]
Message-ID: <87r31ix1im.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20170327133008.GP10606@nuc-i3427.alporthouse.com>

Chris Wilson <chris@chris-wilson.co.uk> writes:

> On Mon, Mar 27, 2017 at 04:19:58PM +0300, Mika Kuoppala wrote:
>> Chris Wilson <chris@chris-wilson.co.uk> writes:
>> 
>> > On Mon, Mar 27, 2017 at 01:12:30PM +0300, Mika Kuoppala wrote:
>> >> Chris Wilson <chris@chris-wilson.co.uk> writes:
>> >> 
>> >> > One POSTING_READ of ACTHD may not be enough to ensure that the seqno
>> >> > write has been posted from the GPU and is now visible. So do three!
>> >> >
>> >> 
>> >> Is this about posting read triggering or just adding enough delay
>> >> that the write gets through?
>> >
>> > It's purely about a delay that we guess will cover 99.9999% of cases.
>> 
>> Acked-by: Mika Kuoppala <mika.kuoppala@intel.com>
>
> Thanks, for checking over the idea. I'm going to apply it to
> topic/core-for-CI for some extended soak testing and see if that
> silences fi-snb-2600

Another thing that would be worth testing is to force a latency guarantee
through pm_qos.

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

  reply	other threads:[~2017-03-27 14:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-25 10:12 [PATCH] drm/i915: Click the ACTHD three times to go home Chris Wilson
2017-03-25 10:29 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-03-27 10:12 ` [PATCH] " Mika Kuoppala
2017-03-27 10:16   ` Chris Wilson
2017-03-27 13:19     ` Mika Kuoppala
2017-03-27 13:30       ` Chris Wilson
2017-03-27 14:00         ` Mika Kuoppala [this message]
2017-03-27 14:25           ` Chris Wilson
2017-03-27 15:02         ` Chris Wilson
2017-03-27 19:05 ` Jani Nikula

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=87r31ix1im.fsf@gaia.fi.intel.com \
    --to=mika.kuoppala@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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 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.