All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	igt-dev@lists.freedesktop.org,
	Ashutosh Dixit <ashutosh.dixit@intel.com>,
	Riana Tauro <riana.tauro@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] i915/i915_power: Sanity check power measurement
Date: Fri, 27 Jan 2023 08:13:14 -0800	[thread overview]
Message-ID: <87mt64ez1h.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20230127122945.yrlacxyfjhqihlua@kamilkon-desk1>

On Fri, 27 Jan 2023 04:29:45 -0800, Kamil Konieczny wrote:
>
> Hi Ashutosh,

Hi Kamil,

I have addressed all comments. Please take a look at the latest
version:

https://patchwork.freedesktop.org/series/113436/

(not sure why Patchwork is creating new series each time).

Thanks.
--
Ashutosh

>
> On 2023-01-26 at 22:25:01 -0800, Ashutosh Dixit wrote:
> > Add a test to sanity check power measurement on integrated/discrete by
> > requiring power under load to be > 0 and >= idle power.
> >
> > v2: Code reorganization (Kamil K)
> >
> > Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> > Reviewed-by: Riana Tauro <riana.tauro@intel.com>
> > ---
> >  tests/i915/i915_power.c | 80 +++++++++++++++++++++++++++++++++++++++++
> >  tests/meson.build       |  1 +
> >  2 files changed, 81 insertions(+)
> >  create mode 100644 tests/i915/i915_power.c
> >
> > diff --git a/tests/i915/i915_power.c b/tests/i915/i915_power.c
> > new file mode 100644
> > index 00000000000..00993cdc846
> > --- /dev/null
> > +++ b/tests/i915/i915_power.c
> > @@ -0,0 +1,80 @@
> > +// SPDX-License-Identifier: MIT
> > +/*
> > + * Copyright © 2023 Intel Corporation
> > + */
> > +
> > +#include "igt.h"
> > +#include "i915/gem.h"
> > +#include "igt_power.h"
> > +
> > +IGT_TEST_DESCRIPTION("i915 power measurement tests");
> > +
> > +static double get_power(struct igt_power *pwr, const char *domain)
> ------------------------------------------------------------- ^
> You are not using this so delete it.

Done.

>
> > +{
> > +	const int sleep_duration_sec = 2;
> ----------------- ^
> Make this a parameter for function.

Done.

>
> > +	struct power_sample sample[2];
> > +
> > +	igt_power_get_energy(pwr, &sample[0]);
> > +	usleep(sleep_duration_sec * USEC_PER_SEC);
> > +	igt_power_get_energy(pwr, &sample[1]);
> > +
> > +	return igt_power_get_mW(pwr, &sample[0], &sample[1]);
> > +}
> > +
> > +static double measure_power(int i915, struct igt_power *pwr,
> > +			    const char *domain, bool load)
> ----------------------------------------------- ^
> This is confusing, delete this. Please avoid creating functions
> with boolean parameter, just do its work in place you will use
> true or false.

Done.

>
> > +{
> > +	const intel_ctx_t *ctx = intel_ctx_create_all_physical(i915);
> > +	uint64_t ahnd = get_reloc_ahnd(i915, ctx->id);
> > +	igt_spin_t *spin;
> > +	double mW;
> > +
> > +	gem_quiescent_gpu(i915);
> > +	if (load) {
> ------- ^
> Delete this if() and move spin creation after idle see below.

Done.

>
> > +		spin = igt_spin_new(i915, .ahnd = ahnd, .ctx = ctx,
> > +				    .engine = ALL_ENGINES,
> > +				    .flags = IGT_SPIN_POLL_RUN);
> > +		/* Wait till at least one spinner starts */
> > +		igt_spin_busywait_until_started(spin);
> > +	}
> > +
> > +	mW = get_power(pwr, domain);
> > +	igt_info("Domain: %s, Load: %d, Measured power: %g mW\n", domain, load, mW);
> > +
> > +	igt_free_spins(i915);
> > +	put_ahnd(ahnd);
> > +	intel_ctx_destroy(i915, ctx);
> > +
> > +	return mW;
> > +}
> > +
> > +static void sanity(int i915, const char *domain)
> > +{
> > +	struct igt_power pwr;
> > +	double idle, busy;
> > +
> > +	igt_require(!igt_power_open(i915, &pwr, domain));
> > +	idle = measure_power(i915, &pwr, domain, false);
> > +	busy = measure_power(i915, &pwr, domain, true);
> > +	igt_power_close(&pwr);
> > +
> > +	igt_assert(idle >= 0 && busy > 0 && busy >= idle);
> ------------------------------------------------ ^
> imho this should be "busy > idle" ?

Done.

>
> Merge sanity() with measure_power() so it will be simple.
> This should look like:
>	// check require
>	// prepare ctx and other
>	idle = get_power(pwr, 2 * USEC_PER_SEC); /* 2 seconds */
>	// create spin and wait until it will run
>	busy = get_power(pwr, 2 * USEC_PER_SEC); /* 2 seconds */
>	// cleanup after spin, ctx, and other
>	// print info what was measured, domain, power and time used
>	// assert

Done.

>
> > +}
> > +
> > +igt_main
> > +{
> > +	int i915;
> > +
> > +	igt_fixture {
> > +		i915 = drm_open_driver_master(DRIVER_INTEL);
> > +	}
> > +
> > +	igt_describe("Sanity check power measurement");
> > +	igt_subtest("sanity") {
> > +		sanity(i915, "gpu");
> ----------------------------- ^
> Do you plan other domains, maybe multi-gpu like gpu-#number ?

Future patch.

>
> Regards,
> Kamil
>
> > +	}
> > +
> > +	igt_fixture {
> > +		close(i915);
> > +	}
> > +}
> > diff --git a/tests/meson.build b/tests/meson.build
> > index cce9d89e1c8..d93a07c9ed6 100644
> > --- a/tests/meson.build
> > +++ b/tests/meson.build
> > @@ -213,6 +213,7 @@ i915_progs = [
> >	'i915_pm_dc',
> >	'i915_pm_rps',
> >	'i915_pm_sseu',
> > +	'i915_power',
> >	'i915_query',
> >	'i915_selftest',
> >	'i915_suspend',
> > --
> > 2.38.0
> >

  reply	other threads:[~2023-01-27 16:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27  6:25 [igt-dev] [PATCH i-g-t 0/2] i915/i915_power: Sanity check power measurement Ashutosh Dixit
2023-01-27  6:25 ` [igt-dev] [PATCH i-g-t 1/2] " Ashutosh Dixit
2023-01-27 12:29   ` Kamil Konieczny
2023-01-27 16:13     ` Dixit, Ashutosh [this message]
2023-01-27  6:25 ` [igt-dev] [PATCH i-g-t 2/2] HAX: Add i915_power@sanity to fast-feedback.testlist Ashutosh Dixit
2023-01-27  7:05 ` [igt-dev] ✓ Fi.CI.BAT: success for i915/i915_power: Sanity check power measurement Patchwork
2023-01-27  8:13 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-01-27 18:09 [igt-dev] [PATCH i-g-t 0/2] " Ashutosh Dixit
2023-01-27 18:09 ` [igt-dev] [PATCH i-g-t 1/2] " Ashutosh Dixit
2023-01-27 16:08 [igt-dev] [PATCH i-g-t 0/2] " Ashutosh Dixit
2023-01-27 16:08 ` [igt-dev] [PATCH i-g-t 1/2] " Ashutosh Dixit
2023-01-27 16:46   ` Kamil Konieczny
2023-01-27 16:55     ` Dixit, Ashutosh
2023-01-27 17:44       ` Kamil Konieczny
2023-01-27 18:12         ` Dixit, Ashutosh
2023-01-21  5:41 [igt-dev] [PATCH i-g-t 0/2] " Ashutosh Dixit
2023-01-21  5:41 ` [igt-dev] [PATCH i-g-t 1/2] " Ashutosh Dixit
2023-01-24 12:59   ` Tauro, Riana
2023-01-24 17:00   ` Kamil Konieczny
2023-01-24 18:01     ` Dixit, Ashutosh
2023-01-25  9:40       ` Kamil Konieczny
2023-01-27  6:28         ` Dixit, Ashutosh

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=87mt64ez1h.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --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.