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: [PATH i-g-t v12 2/2] tests: add slice power programming test
Date: Thu, 13 Sep 2018 11:38:47 +0100	[thread overview]
Message-ID: <ad7750a8-3820-6f2b-8cbd-ed59901b3bb5@linux.intel.com> (raw)
In-Reply-To: <153675322311.13043.17778315701113692275@skylake-alporthouse-com>


On 12/09/2018 12:53, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2018-09-11 15:42:10)
>> +       last_with_engines = -1;
>> +       for (class = 0; class < ~0; class++) {
>> +               for (instance = 0; instance < ~0; instance++) {
>> +                       int ret;
>> +
>> +                       sseu.class = class;
>> +                       sseu.instance = instance;
>> +
>> +                       ret = __gem_context_set_param(fd, &arg);
>> +
>> +                       if (has_engine(fd, class, instance)) {
>> +                               if (engine_supports_sseu(fd, class, instance))
> 
> Meh, <rant>. I just don't like having hardcoded db on this side of the
> ABI. The ABI imo is to ask the kernel if the device/engine is supported,
> and should not allow for assumptions.

Done.

>> +static void
>> +test_dynamic(int fd, unsigned int flags)
>> +{
>> +       uint64_t pg_slice_mask = mask_minus_one(__slice_mask__);
>> +       unsigned int pg_slice_count = __slice_count__ - 1;
>> +       struct drm_i915_gem_context_param_sseu sseu = { };
>> +       struct drm_i915_gem_context_param arg =
>> +               { .param = I915_CONTEXT_PARAM_SSEU,
>> +                 .ctx_id = gem_context_create(fd),
>> +                 .size = sizeof(sseu),
>> +                 .value = to_user_pointer(&sseu) };
>> +       igt_spin_t *spin = NULL;
>> +
>> +       gem_context_get_param(fd, &arg);
>> +
>> +       /* First set the default mask */
>> +       if (flags & TEST_BUSY)
>> +               spin = __spin_sync(fd, arg.ctx_id, I915_EXEC_RENDER);
>> +
>> +       sseu.slice_mask = __slice_mask__;
>> +       gem_context_set_param(fd, &arg);
> 
> I would also suggest a reset test here. Both reset when idle, and by
> hangcheck/forced-reset of the spinner & active context.
> 
> And across suspend.

Reset & suspsend after set param but before execbuf? Or after execbuf 
and then re-read rpcs?

>> +       igt_assert_eq(read_slice_count_busy(fd, arg.ctx_id, 0, spin),
>> +                     __slice_count__);
>> +       igt_assert_eq(read_slice_count(fd, 0, 0), __slice_count__);
> 
> In the read_slice I would suggest having a
> igt_assert(gem_bo_busy(spin->handle));

Done.

Regards,

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

  reply	other threads:[~2018-09-13 10:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-05 14:25 [PATH i-g-t 0/2] Per context dynamic (sub)slice power-gating Tvrtko Ursulin
2018-09-05 14:25 ` [PATH i-g-t 1/2] headers: bump Tvrtko Ursulin
2018-09-05 14:25 ` [PATH i-g-t 2/2] tests: add slice power programming test Tvrtko Ursulin
2018-09-05 22:57   ` [igt-dev] " Chris Wilson
2018-09-06  7:00   ` Chris Wilson
2018-09-06  9:31     ` Tvrtko Ursulin
2018-09-06  9:50       ` Chris Wilson
2018-09-11 11:34         ` [PATH i-g-t v11 " Tvrtko Ursulin
2018-09-11 11:45           ` [igt-dev] " Chris Wilson
2018-09-11 12:00             ` Tvrtko Ursulin
2018-09-11 14:42               ` [PATH i-g-t v12 " Tvrtko Ursulin
2018-09-12 11:53                 ` Chris Wilson
2018-09-13 10:38                   ` Tvrtko Ursulin [this message]
2018-09-13 10:48                     ` Chris Wilson
2018-09-14 16:04                 ` [PATCH i-g-t v13 2/2] tests/gem_ctx_sseu: Dynamic (sub)slice programming tests Tvrtko Ursulin
2018-09-14 16:07                   ` [igt-dev] " Chris Wilson
2018-09-14 16:17                   ` Chris Wilson
2018-09-17  9:33                     ` Tvrtko Ursulin
2018-09-17 10:38                       ` Chris Wilson
2018-09-17 11:28                     ` [PATCH i-g-t v14 " Tvrtko Ursulin
2018-09-17 12:04                       ` [igt-dev] " Chris Wilson
2018-09-18 13:41                       ` [PATCH i-g-t v15 " Tvrtko Ursulin

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=ad7750a8-3820-6f2b-8cbd-ed59901b3bb5@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