public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	igt-dev@lists.freedesktop.org
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v6] tests/perf_pmu: Verify engine busyness accuracy
Date: Mon, 19 Feb 2018 09:19:47 +0000	[thread overview]
Message-ID: <e7ceaeb2-749c-e242-2fbd-14331ec64363@linux.intel.com> (raw)
In-Reply-To: <151886739754.7225.6485916433861922944@mail.alporthouse.com>


On 17/02/2018 11:36, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2018-02-15 15:34:53)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> A subtest to verify that the engine busyness is reported with expected
>> accuracy on platforms where the feature is available.
>>
>> We test three patterns: 2%, 50% and 98% load per engine.
>>
>> v2:
>>   * Use spin batch instead of nop calibration.
>>   * Various tweaks.
>>
>> v3:
>>   * Change loops to be time based.
>>   * Use __igt_spin_batch_new inside timing sensitive loops.
>>   * Fixed PWM sleep handling.
>>
>> v4:
>>   * Use restarting spin batch.
>>   * Calibrate more carefully by looking at the real PWM loop.
>>
>> v5:
>>   * Made standalone.
>>   * Better info messages.
>>   * Tweak sleep compensation.
>>
>> v6:
>>   * Some final tweaks. (Chris Wilson)
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
>> ---
>> +
>> +       /* Sampling platforms cannot reach the high accuracy criteria. */
>> +       igt_require(gem_has_execlists(gem_fd));
> 
> But we don't handle guc, right?

Correct.

> igt_skip_on(gem_has_guc_submission(gem_fd)) ?

I'll dig up and rebase my old patch which implements busy stats in GuC 
mode.

> https://intel-gfx-ci.01.org/tree/drm-tip/kasan_2/fi-skl-guc/igt@perf_pmu@busy-accuracy-2-vecs0.html
> 
> Or at least it doesn't work to sufficient accuracy. And bsw hung.

There are some occasional excursions over 15% tolerance even with 
execlists on small core. Bummer. Don't want to be playing up the 
tolerance game. I'll analyse in more detail and think what to do.

Do you have a link to BSW hang? Is that obviously related to PMU?

Regards,

Tvrtko


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

  reply	other threads:[~2018-02-19  9:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15 11:53 [PATCH i-g-t] tests/perf_pmu: Verify engine busyness accuracy Tvrtko Ursulin
2018-02-15 12:43 ` Chris Wilson
2018-02-15 15:34   ` [PATCH i-g-t v6] " Tvrtko Ursulin
2018-02-17 11:36     ` [igt-dev] " Chris Wilson
2018-02-19  9:19       ` Tvrtko Ursulin [this message]
2018-02-19  9:27         ` Chris Wilson
2018-02-19  9:57           ` Tvrtko Ursulin
2018-02-19 10:26             ` Chris Wilson
2018-02-19 10:58               ` Tvrtko Ursulin
2018-02-19 11:04                 ` Chris Wilson

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=e7ceaeb2-749c-e242-2fbd-14331ec64363@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=tursulin@ursulin.net \
    /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