All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tvrtko Ursulin <tursulin@ursulin.net>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	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:48:00 +0100	[thread overview]
Message-ID: <153683568037.31648.14665328939907661004@skylake-alporthouse-com> (raw)
In-Reply-To: <ad7750a8-3820-6f2b-8cbd-ed59901b3bb5@linux.intel.com>

Quoting Tvrtko Ursulin (2018-09-13 11:38:47)
> 
> On 12/09/2018 12:53, Chris Wilson wrote:
> > Quoting Tvrtko Ursulin (2018-09-11 15:42:10)
> > 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?

My concern is making sure that after the reset/suspend the adjusted sseu
is still in effect.

For reset, I think the hardest case is if the spinning batch (causing us
to use the MI_STORE_DATA_IMM path) itself hangs. An idle/reset is only
borderline interesting. For that it's just the question of whether
resetting the gpu breaks everything -- but we reset the gpu frequently
enough (on load, on resume) that there's no getting away from it :)

Argh, there's another dilemma here... The wedged driver. In that case,
it should still work as although we may lose the request to set the sseu
in flight, if we ever use the gpu again, we will repin the context and
so reset the sseu.

For suspend, I can see an argument for both idle/suspend and
active/suspend to check that the settings are preserved across the
suspend. In the first case, the path we take will apply them afterwards,
in the latter case, we will apply the settings again on resume. So maybe
there isn't much point to the second case. However, it does all presume
that we do remember to repin the context (so probably worth exercising).
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tvrtko Ursulin <tursulin@ursulin.net>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	igt-dev@lists.freedesktop.org
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [igt-dev] [Intel-gfx] [PATH i-g-t v12 2/2] tests: add slice power programming test
Date: Thu, 13 Sep 2018 11:48:00 +0100	[thread overview]
Message-ID: <153683568037.31648.14665328939907661004@skylake-alporthouse-com> (raw)
In-Reply-To: <ad7750a8-3820-6f2b-8cbd-ed59901b3bb5@linux.intel.com>

Quoting Tvrtko Ursulin (2018-09-13 11:38:47)
> 
> On 12/09/2018 12:53, Chris Wilson wrote:
> > Quoting Tvrtko Ursulin (2018-09-11 15:42:10)
> > 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?

My concern is making sure that after the reset/suspend the adjusted sseu
is still in effect.

For reset, I think the hardest case is if the spinning batch (causing us
to use the MI_STORE_DATA_IMM path) itself hangs. An idle/reset is only
borderline interesting. For that it's just the question of whether
resetting the gpu breaks everything -- but we reset the gpu frequently
enough (on load, on resume) that there's no getting away from it :)

Argh, there's another dilemma here... The wedged driver. In that case,
it should still work as although we may lose the request to set the sseu
in flight, if we ever use the gpu again, we will repin the context and
so reset the sseu.

For suspend, I can see an argument for both idle/suspend and
active/suspend to check that the settings are preserved across the
suspend. In the first case, the path we take will apply them afterwards,
in the latter case, we will apply the settings again on resume. So maybe
there isn't much point to the second case. However, it does all presume
that we do remember to repin the context (so probably worth exercising).
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

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

Thread overview: 55+ 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 ` [igt-dev] " Tvrtko Ursulin
2018-09-05 14:25 ` [PATH i-g-t 1/2] headers: bump Tvrtko Ursulin
2018-09-05 14:25   ` [igt-dev] " Tvrtko Ursulin
2018-09-05 14:25 ` [PATH i-g-t 2/2] tests: add slice power programming test Tvrtko Ursulin
2018-09-05 14:25   ` [igt-dev] " Tvrtko Ursulin
2018-09-05 22:57   ` Chris Wilson
2018-09-05 22:57     ` Chris Wilson
2018-09-06  7:00   ` Chris Wilson
2018-09-06  7:00     ` Chris Wilson
2018-09-06  9:31     ` Tvrtko Ursulin
2018-09-06  9:31       ` [igt-dev] [Intel-gfx] " Tvrtko Ursulin
2018-09-06  9:50       ` [igt-dev] " Chris Wilson
2018-09-06  9:50         ` [igt-dev] [Intel-gfx] " Chris Wilson
2018-09-11 11:34         ` [PATH i-g-t v11 " Tvrtko Ursulin
2018-09-11 11:34           ` [igt-dev] " Tvrtko Ursulin
2018-09-11 11:45           ` Chris Wilson
2018-09-11 11:45             ` Chris Wilson
2018-09-11 12:00             ` Tvrtko Ursulin
2018-09-11 12:00               ` [Intel-gfx] " Tvrtko Ursulin
2018-09-11 14:42               ` [PATH i-g-t v12 " Tvrtko Ursulin
2018-09-11 14:42                 ` [igt-dev] " Tvrtko Ursulin
2018-09-12 11:53                 ` Chris Wilson
2018-09-12 11:53                   ` [igt-dev] [Intel-gfx] " Chris Wilson
2018-09-13 10:38                   ` Tvrtko Ursulin
2018-09-13 10:38                     ` [igt-dev] [Intel-gfx] " Tvrtko Ursulin
2018-09-13 10:48                     ` Chris Wilson [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:04                   ` [Intel-gfx] " Tvrtko Ursulin
2018-09-14 16:07                   ` [igt-dev] " Chris Wilson
2018-09-14 16:07                     ` Chris Wilson
2018-09-14 16:17                   ` Chris Wilson
2018-09-14 16:17                     ` Chris Wilson
2018-09-17  9:33                     ` Tvrtko Ursulin
2018-09-17  9:33                       ` [Intel-gfx] " Tvrtko Ursulin
2018-09-17 10:38                       ` Chris Wilson
2018-09-17 10:38                         ` [Intel-gfx] " Chris Wilson
2018-09-17 11:28                     ` [PATCH i-g-t v14 " Tvrtko Ursulin
2018-09-17 11:28                       ` [Intel-gfx] " Tvrtko Ursulin
2018-09-17 12:04                       ` [igt-dev] " Chris Wilson
2018-09-17 12:04                         ` Chris Wilson
2018-09-18 13:41                       ` [PATCH i-g-t v15 " Tvrtko Ursulin
2018-09-18 13:41                         ` [igt-dev] " Tvrtko Ursulin
2018-09-05 16:46 ` [igt-dev] ✓ Fi.CI.BAT: success for Per context dynamic (sub)slice power-gating Patchwork
2018-09-05 22:44 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-09-11 18:13 ` [igt-dev] ✓ Fi.CI.BAT: success for Per context dynamic (sub)slice power-gating (rev3) Patchwork
2018-09-11 23:31 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-09-14 17:22 ` [igt-dev] ✓ Fi.CI.BAT: success for Per context dynamic (sub)slice power-gating (rev4) Patchwork
2018-09-14 22:22 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2018-09-17 12:21 ` [igt-dev] ✗ Fi.CI.BAT: failure for Per context dynamic (sub)slice power-gating (rev5) Patchwork
2018-09-17 18:21 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2018-09-17 20:43 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-09-18 14:02 ` [igt-dev] ✓ Fi.CI.BAT: success for Per context dynamic (sub)slice power-gating (rev6) Patchwork
2018-09-18 15:18 ` [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=153683568037.31648.14665328939907661004@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=tursulin@ursulin.net \
    --cc=tvrtko.ursulin@linux.intel.com \
    /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.