From: Caz Yokoyama <Caz.Yokoyama@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v2 1/1] i915_pm_rpm: gem-execbuf-stress-extra-wait faster
Date: Tue, 12 Mar 2019 08:14:53 -0700 [thread overview]
Message-ID: <7548c4d90ef7850e76bae7e9f6ab5ed1547b7641.camel@intel.com> (raw)
In-Reply-To: <8be54d05ca05a50b163392c006074bce2deae9cd.1552361435.git.caz.yokoyama@intel.com>
The corresponding patch is subjected as "[PATCH v2 2/2] add
DROP_SUSPEND".
The patch in i915_drop_caches_set() is the first part
of pm_runtime_force_suspend(). After GPU becomes suspended state,
pm_runtime_status_suspended(dev) is always true and get out. In other
words, the patch and pm_runtime_force_suspend() are equivalent on
suspended state.
As a result, I prefer to remove gem-execbuf-stress-extra-wait subtest
because it does same as gem-execbuf-stress except for meaningless (10 x
5 sec) delay.
Chris, how do you think?
-caz
On Tue, 2019-03-12 at 03:31 +0000, Caz Yokoyama wrote:
> With the corresponding patch in drm-tip,
> confirm there is no additional work needed when
> GPU is in suspended state.
>
> Signed-off-by: Caz Yokoyama <caz.yokoyama@intel.com>
> ---
> lib/igt_debugfs.h | 7 +++++++
> tests/i915/i915_pm_rpm.c | 7 +++++--
> 2 files changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/lib/igt_debugfs.h b/lib/igt_debugfs.h
> index b9cf0f81..9fa38b42 100644
> --- a/lib/igt_debugfs.h
> +++ b/lib/igt_debugfs.h
> @@ -216,6 +216,13 @@ void igt_require_hpd_storm_ctl(int fd);
> DROP_FREED | \
> DROP_IDLE)
>
> +/**
> + * DROP_SUSPEND:
> + *
> + * force to suspended state.
> + */
> +#define DROP_SUSPEND 0x200
> +
> void igt_reset_fifo_underrun_reporting(int drm_fd);
>
> bool igt_drop_caches_has(int fd, uint64_t val);
> diff --git a/tests/i915/i915_pm_rpm.c b/tests/i915/i915_pm_rpm.c
> index be296f52..79528d18 100644
> --- a/tests/i915/i915_pm_rpm.c
> +++ b/tests/i915/i915_pm_rpm.c
> @@ -1338,12 +1338,15 @@ static void gem_execbuf_stress_subtest(int
> rounds, int wait_flags)
> for (i = 0; i < rounds; i++) {
> gem_execbuf(drm_fd, &execbuf);
>
> + igt_drop_caches_set(drm_fd, DROP_IDLE); /* clean up
> idle work */
> if (wait_flags & WAIT_STATUS)
> igt_assert(wait_for_suspended());
> if (wait_flags & WAIT_PC8_RES)
> igt_assert(pc8_plus_residency_changed(30));
> - if (wait_flags & WAIT_EXTRA)
> - sleep(5);
> + if (wait_flags & WAIT_EXTRA) {
> + /* force to suspend mode */
> + igt_drop_caches_set(drm_fd, DROP_SUSPEND);
> + }
> }
>
> gem_close(drm_fd, handle);
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-03-12 15:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 3:31 [igt-dev] [PATCH i-g-t v2 1/1] i915_pm_rpm: gem-execbuf-stress-extra-wait faster Caz Yokoyama
2019-03-12 3:31 ` [igt-dev] [PATCH v2 2/2] add DROP_SUSPEND Caz Yokoyama
2019-03-12 15:30 ` Chris Wilson
2019-03-12 15:52 ` Caz Yokoyama
2019-03-12 15:51 ` Chris Wilson
2019-03-12 16:11 ` Caz Yokoyama
2019-03-12 16:09 ` Chris Wilson
2019-03-12 17:14 ` Caz Yokoyama
2019-03-12 22:36 ` Caz Yokoyama
2019-03-12 22:42 ` Chris Wilson
2019-03-12 15:14 ` Caz Yokoyama [this message]
2019-03-12 15:24 ` [igt-dev] [PATCH i-g-t v2 1/1] i915_pm_rpm: gem-execbuf-stress-extra-wait faster 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=7548c4d90ef7850e76bae7e9f6ab5ed1547b7641.camel@intel.com \
--to=caz.yokoyama@intel.com \
--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