From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "Tauro, Riana" <riana.tauro@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"Nilawar, Badal" <badal.nilawar@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] i915/i915_power: Measure GPU idle/busy power
Date: Wed, 18 Jan 2023 19:32:19 -0800 [thread overview]
Message-ID: <87o7qvurlo.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <bddffb35-4a95-58c5-473d-5904fb1dfc84@intel.com>
On Tue, 17 Jan 2023 23:22:46 -0800, Tauro, Riana wrote:
>
> Hi Ashutosh
>
Hi Riana,
> Energy measurement when idle and with workload is also a part of rc6-idle
> test. Why do we need new tests?
We want to be able to measure max/peak power.
rc6-idle has this:
static void bg_load()
{
...
/* aim for ~1% busy */
Therefore it measures this:
[adixit@DUT1220-DG2SVC igt-gpu-tools]$ sudo ./build/tests/i915_pm_rc6_residency --r rc6-idle
IGT-Version: 1.27-g369bb6fb0f (x86_64) (Linux: 5.15.47+ x86_64)
Opened device: /dev/dri/card0
Starting subtest: rc6-idle
Starting dynamic subtest: gt0-rcs0
Total energy used while idle: 85825.3mJ (28606.5mW)
Total energy used for normal: 86731.6mJ (28908.6mW)
Total energy used for boost: 86992.8mJ (28995.8mW)
Total energy used for once: 86677.9mJ (28890.5mW)
Dynamic subtest gt0-rcs0: SUCCESS (12.235s)
The new test measures this:
[adixit@DUT1220-DG2SVC igt-gpu-tools]$ sudo ./build/tests/i915_power
IGT-Version: 1.27-g369bb6fb0f (x86_64) (Linux: 5.15.47+ x86_64)
Opened device: /dev/dri/card0
Starting subtest: gpu-idle
Measured power: 28535.5 mW
Subtest gpu-idle: SUCCESS (3.002s)
Starting subtest: gpu-busy
Measured power: 50331.9 mW
Subtest gpu-busy: SUCCESS (3.008s)
So you can see rc6-idle basically measures idle power (28 W instead of 50
W), not power under load.
Other tests such as gem_exec_schedule also have igt_require etc. which skip
in all sorts of situations. That is why I was forced to write these simple
new tests.
Thanks.
--
Ashutosh
next prev parent reply other threads:[~2023-01-19 3:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 19:03 [igt-dev] [PATCH i-g-t] i915/i915_power: Measure GPU idle/busy power Ashutosh Dixit
2023-01-17 20:54 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-01-18 6:30 ` [igt-dev] [PATCH i-g-t] " Gupta, Anshuman
2023-01-18 7:22 ` Tauro, Riana
2023-01-19 3:32 ` Dixit, Ashutosh [this message]
2023-01-23 5:46 ` Tauro, Riana
2023-01-19 5:07 ` Dixit, Ashutosh
2023-01-18 10:29 ` [igt-dev] ✓ Fi.CI.IGT: success for " 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=87o7qvurlo.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=badal.nilawar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox