public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/perf: Fix timeout for RC6 re-enabling
Date: Tue, 16 Apr 2019 17:01:13 +0300	[thread overview]
Message-ID: <20190416140113.GC6969@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <155542301901.25605.14851395126471892312@skylake-alporthouse-com>

On Tue, Apr 16, 2019 at 02:56:59PM +0100, Chris Wilson wrote:
> Quoting Imre Deak (2019-04-16 14:51:35)
> > After closing the perf stream the parking the GPU engines may easily
> > take more than 1 second: releasing the FD itself results in a new
> > request submission via i915_perf_release()->i915_oa_stream_destroy()->
> > gen8_disable_metric_set(). That means a >1sec delay for the delayed
> > unpark to be called due to the delay from
> 
> igt_drop_caches_set(DROP_IDLE);
> 
> flushes the idle work handler immediately, though you will probably want
> DROP_ACTIVE | DROP_RETIRE to complete the picture, see
> gem_quiescent_gpu().

Thanks, seems to work, will respin with that. 

--Imre
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-04-16 14:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 13:51 [igt-dev] [PATCH i-g-t] tests/perf: Fix timeout for RC6 re-enabling Imre Deak
2019-04-16 13:56 ` Chris Wilson
2019-04-16 14:01   ` Imre Deak [this message]
2019-04-16 14:03 ` Lionel Landwerlin
2019-04-16 14:09 ` [igt-dev] [PATCH v2] " Imre Deak
2019-04-16 14:12   ` Lionel Landwerlin
2019-04-16 14:47 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/perf: Fix timeout for RC6 re-enabling (rev2) Patchwork
2019-04-16 15:28   ` Imre Deak
2019-04-16 21:08 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20190416140113.GC6969@ideak-desk.fi.intel.com \
    --to=imre.deak@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@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