From: "Gupta, Anshuman" <anshuman.gupta@intel.com>
To: "Tauro, Riana" <riana.tauro@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 2/2] tests/i915/pm_rc6_residency: Modify rc6_fence to use intel_ctx_t from igt_fixture
Date: Tue, 21 Jun 2022 10:19:19 +0000 [thread overview]
Message-ID: <83728cd3731e4b9e89cbec7dc87f3e64@intel.com> (raw)
In-Reply-To: <20220621100606.2037879-3-riana.tauro@intel.com>
> -----Original Message-----
> From: Tauro, Riana <riana.tauro@intel.com>
> Sent: Tuesday, June 21, 2022 3:36 PM
> To: igt-dev@lists.freedesktop.org
> Cc: Tauro, Riana <riana.tauro@intel.com>; Gupta, Anshuman
> <anshuman.gupta@intel.com>; Dixit, Ashutosh <ashutosh.dixit@intel.com>
> Subject: [PATCH i-g-t 2/2] tests/i915/pm_rc6_residency: Modify rc6_fence to
> use intel_ctx_t from igt_fixture
>
> Modify rc6_fence test to use intel_ctx_t from igt_fixture
Commit message can be more descriptive , this should be non-functional patch.
We are not doing any functional change to patch.
Also this should be the first patch of the series,
which create and destroy the context in igt_fixture and rc6_fences will use the same ctx,
Followed by second patch.
Regards,
Anshuman Gupta.
>
> Signed-off-by: Riana Tauro <riana.tauro@intel.com>
> ---
> tests/i915/i915_pm_rc6_residency.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/tests/i915/i915_pm_rc6_residency.c
> b/tests/i915/i915_pm_rc6_residency.c
> index 560b635f..043370cc 100644
> --- a/tests/i915/i915_pm_rc6_residency.c
> +++ b/tests/i915/i915_pm_rc6_residency.c
> @@ -450,13 +450,12 @@ static void rc6_idle(int i915, uint64_t flags)
> }
> }
>
> -static void rc6_fence(int i915)
> +static void rc6_fence(int i915, const intel_ctx_t *ctx)
> {
> const int64_t duration_ns = SLEEP_DURATION *
> (int64_t)NSEC_PER_SEC;
> const int tolerance = 20; /* Some RC6 is better than none! */
> const unsigned int gen = intel_gen(intel_get_drm_devid(i915));
> const struct intel_execution_engine2 *e;
> - const intel_ctx_t *ctx;
> struct power_sample sample[2];
> unsigned long slept;
> uint64_t rc6, ts[2], ahnd;
> @@ -486,7 +485,6 @@ static void rc6_fence(int i915)
> assert_within_epsilon(rc6, ts[1] - ts[0], 5);
>
> /* Submit but delay execution, we should be idle and conserving power
> */
> - ctx = intel_ctx_create_all_physical(i915);
> ahnd = get_reloc_ahnd(i915, ctx->id);
> for_each_ctx_engine(i915, ctx, e) {
> igt_spin_t *spin;
> @@ -525,7 +523,6 @@ static void rc6_fence(int i915)
> assert_within_epsilon(rc6, ts[1] - ts[0], tolerance);
> gem_quiescent_gpu(i915);
> }
> - intel_ctx_destroy(i915, ctx);
> put_ahnd(ahnd);
>
> rapl_close(&rapl);
> @@ -560,7 +557,7 @@ igt_main
> igt_require_gem(i915);
> gem_quiescent_gpu(i915);
>
> - rc6_fence(i915);
> + rc6_fence(i915, ctx);
> }
>
> igt_subtest_group {
> --
> 2.25.1
next prev parent reply other threads:[~2022-06-21 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 10:06 [igt-dev] [PATCH i-g-t 0/2] Extend i915_pm_rc6_residency Riana Tauro
2022-06-21 10:06 ` [igt-dev] [PATCH i-g-t 1/2] tests/i915/pm_rc6_residency: Extend rc6-idle test on remaining engines Riana Tauro
2022-06-21 10:06 ` [igt-dev] [PATCH i-g-t 2/2] tests/i915/pm_rc6_residency: Modify rc6_fence to use intel_ctx_t from igt_fixture Riana Tauro
2022-06-21 10:19 ` Gupta, Anshuman [this message]
2022-06-21 11:02 ` [igt-dev] ✓ Fi.CI.BAT: success for Extend i915_pm_rc6_residency Patchwork
2022-06-21 19:38 ` [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=83728cd3731e4b9e89cbec7dc87f3e64@intel.com \
--to=anshuman.gupta@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=riana.tauro@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.