From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Anshuman Gupta <anshuman.gupta@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v6 2/4] tests/i915/i915_pm_rpm: modeset-pc8-residency-stress
Date: Fri, 26 Apr 2019 20:59:43 +0300 [thread overview]
Message-ID: <20190426175943.GT24299@intel.com> (raw)
In-Reply-To: <1556300726-20254-3-git-send-email-anshuman.gupta@intel.com>
On Fri, Apr 26, 2019 at 11:15:24PM +0530, Anshuman Gupta wrote:
> Introduced pc8_needs_screen_off flag in order to differentiate
> between HASWELL/BROADWELL and AT_LEAST_GEN9. GEN9 onwards
> PC8+ residency does't require display to be turned on.
Why are we so fixated on pc8? Shouldn't we just check that we reach
the max package c-state with displays off?
>
> v3:Removed pc8_needs_screen_off from mode_set_data structure,
> made it global, aligning to has_pc8 and has_runtime_pm globals. [Ram]
> Made modeset_subtest() to tests PC8+ residency after enabling a screen,
> earlier it expects PC8+ residency to stop on HSW/BDW.
>
> v4:Fixed conditional code for pc8_needs_screen_off. [Ram]
> Used macros for timeout values, given to PC8+ residency check function. [Ram]
> Changed the screen on timeout to check pc8+ residency to 10 seconds.
>
> Signed-off-by: Anshuman Gupta <anshuman.gupta@intel.com>
> ---
> tests/i915/i915_pm_rpm.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/tests/i915/i915_pm_rpm.c b/tests/i915/i915_pm_rpm.c
> index 9315dbd..bd13d21 100644
> --- a/tests/i915/i915_pm_rpm.c
> +++ b/tests/i915/i915_pm_rpm.c
> @@ -907,7 +907,7 @@ static void modeset_subtest(enum screen_type type, int rounds, int wait_flags)
> if (wait_flags & WAIT_STATUS)
> igt_assert(wait_for_suspended());
> if (wait_flags & WAIT_PC8_RES)
> - igt_assert(pc8_plus_residency_changed(30));
> + igt_assert(pc8_plus_residency_changed(TIME_OUT_SEC_30));
> if (wait_flags & WAIT_EXTRA)
> sleep(5);
>
> @@ -917,7 +917,13 @@ static void modeset_subtest(enum screen_type type, int rounds, int wait_flags)
> if (wait_flags & WAIT_STATUS)
> igt_assert(wait_for_active());
> if (wait_flags & WAIT_PC8_RES)
> - igt_assert(!pc8_plus_residency_changed(5));
> + if (pc8_needs_screen_off)
> + igt_assert(!pc8_plus_residency_changed
> + (TIME_OUT_SEC_5));
> + else
> + igt_assert(pc8_plus_residency_changed
> + (TIME_OUT_SEC_10));
> +
> if (wait_flags & WAIT_EXTRA)
> sleep(5);
> }
> --
> 2.7.4
>
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
--
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-04-26 17:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 17:45 [igt-dev] [PATCH i-g-t v6 0/4] Enabling PC8+ residency for all GEN9+ platforms v6 Anshuman Gupta
2019-04-26 17:45 ` [igt-dev] [PATCH i-g-t v6 1/4] tests/i915/i915_pm_rpm: Enable PC8+ residency test for all Gen9+ Anshuman Gupta
2019-05-03 10:46 ` Ramalingam C
2019-04-26 17:45 ` [igt-dev] [PATCH i-g-t v6 2/4] tests/i915/i915_pm_rpm: modeset-pc8-residency-stress Anshuman Gupta
2019-04-26 17:59 ` Ville Syrjälä [this message]
2019-04-27 6:35 ` Gupta, Anshuman
2019-05-03 10:51 ` Ramalingam C
2019-04-26 17:45 ` [igt-dev] [PATCH i-g-t v6 3/4] DEBUG: invoke powertop and pmc ltr_ignore when pc8 tests fails Anshuman Gupta
2019-04-26 17:45 ` [igt-dev] [PATCH i-g-t v6 4/4] DO_NOT_MERGE: adding i915_pm_rpm pc8 subtest to fast feedback list Anshuman Gupta
2019-04-26 18:43 ` [igt-dev] ✗ Fi.CI.BAT: failure for Enabling PC8+ residency for all GEN9+ platforms (rev6) Patchwork
2019-04-29 5:18 ` Gupta, Anshuman
2019-04-29 11:13 ` Peres, Martin
2019-04-29 11:10 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2019-04-29 14:09 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=20190426175943.GT24299@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=anshuman.gupta@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