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] [PATH i-g-t v11 2/2] tests: add slice power programming test
Date: Tue, 11 Sep 2018 13:00:31 +0100	[thread overview]
Message-ID: <151852f9-36b4-cdec-58c0-d7b5e30cfc2e@linux.intel.com> (raw)
In-Reply-To: <153666635083.4253.10909960072957104960@skylake-alporthouse-com>


On 11/09/2018 12:45, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2018-09-11 12:34:17)
>> +igt_main
>> +{
>> +       unsigned int max_slices = 3, max_subslices = 3;
>> +       unsigned int i;
>> +       int fd;
>> +
>> +       igt_fixture {
>> +               fd = drm_open_driver(DRIVER_INTEL);
>> +               igt_require_gem(fd);
>> +
>> +               __intel_devid__ = intel_get_drm_devid(fd);
>> +               __intel_gen__ = intel_gen(__intel_devid__);
>> +
>> +               igt_require(kernel_has_per_context_sseu_support(fd));
>> +       }
>> +
>> +       igt_subtest_group {
>> +               igt_fixture {
>> +                       igt_require(!platform_has_per_context_sseu_support());
> 
> Why does the kernel say that the platform has context sseu support?

Note sure what are you aiming at. Here I have a subgroup of tests (well 
one) which test that the kernel and IGT expectation of which platforms 
should support the feature match.

Regards,

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

  reply	other threads:[~2018-09-11 12:00 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 [this message]
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
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=151852f9-36b4-cdec-58c0-d7b5e30cfc2e@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