Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Riana Tauro <riana.tauro@intel.com>
To: <sk.anirban@intel.com>, <igt-dev@lists.freedesktop.org>,
	<anshuman.gupta@intel.com>
Subject: Re: [i-g-t,v3,1/2] tests/intel/xe_pm_residency: Add GT coarse power gating validation
Date: Tue, 22 Oct 2024 15:20:15 +0530	[thread overview]
Message-ID: <44bce885-d0bf-4186-b8a6-9ff2acc86dfc@intel.com> (raw)
In-Reply-To: <20241021071902.2086909-2-sk.anirban@intel.com>

Hi Anirban

On 10/21/2024 12:49 PM, sk.anirban@intel.com wrote:
> From: Sk Anirban <sk.anirban@intel.com>
> 
> Implement test cpg-basic to validate coarse power gating status
> after S3 cycle.
> Add test cpg-gt-toggle to check if GT coarse power gating is up when
> forcewake is acquired and down when released.
> 
> v2: Address cosmetic review comments (Riana)
>      Fix suspend state (Riana)
>      Add exit handler for test cpg-gt-toggle (Riana)
> 
> v3: Address cosmetic review comments (Riana)
>      Fix commit message & test name (Konieczny)
> 
> Signed-off-by: Sk Anirban <sk.anirban@intel.com>
> ---
>   tests/intel/xe_pm_residency.c | 92 +++++++++++++++++++++++++++++++++++
>   1 file changed, 92 insertions(+)
> 
> diff --git a/tests/intel/xe_pm_residency.c b/tests/intel/xe_pm_residency.c
> index 772fe9b57..29316514a 100644
> --- a/tests/intel/xe_pm_residency.c
> +++ b/tests/intel/xe_pm_residency.c
> @@ -63,6 +63,12 @@ enum test_type {
>    * SUBTEST: toggle-gt-c6
>    * Description: toggles GT C states by acquiring/releasing forcewake,
>    *		also validates power consumed by GPU in GT C6 is lesser than that of GT C0.
> + *
> + * SUBTEST: cpg-basic
> + * Description: Validate GT coarse power gating status with S3 cycle.
> + *
> + * SUBTEST: cpg-gt-toggle
> + * Description: Toggle GT coarse power gating states by acquiring/releasing forcewake.
>    */
>   IGT_TEST_DESCRIPTION("Tests for gtidle properties");
>   
> @@ -317,6 +323,81 @@ static void toggle_gt_c6(int fd, int n)
>   			     "Power consumed in GT C6 should be lower than GT C0\n");
>   }
>   
> +
> +static void cpg_enabled(int fd, int gt)
> +{
> +	int dir;
> +	char str[512], path[64], *render_substr, *media_substr;
> +	const char *render_power_gating = "Render Power Gating Enabled: ";
> +	const char *media_power_gating = "Media Power Gating Enabled: ";
> +
> +	dir = igt_debugfs_gt_dir(fd, gt);
> +	igt_assert(dir >= 0);
> +
> +	snprintf(path, sizeof(path), "gt%d/powergate_info", gt);
> +	igt_debugfs_read(fd, path, str);
> +	close(dir);
> +
> +	render_substr = strstr(str, render_power_gating);
> +	if (render_substr)
> +		igt_assert_f(strncmp(render_substr + strlen(render_power_gating), "yes", 3) == 0,
> +			     "Render Power Gating should be enabled");
> +
> +	media_substr = strstr(str, media_power_gating);
> +	if (media_substr)
> +		igt_assert_f(strncmp(media_substr + strlen(media_power_gating), "yes", 3) == 0,
> +			     "Media Power Gating should be enabled");
> +}
> +
> +
> +static void powergate_status(int fd, int gt, const char *expected_status)
> +{
> +	int dir;
> +	char str[512], path[64], *status_substr;
use PATH_MAX here
> +	const char *power_gate_status = "Power Gate Status: ";
> +
> +	dir = igt_debugfs_gt_dir(fd, gt);
> +	igt_assert(dir >= 0);
> +
> +	snprintf(path, sizeof(path), "gt%d/powergate_info", gt);
> +	igt_debugfs_read(fd, path, str);
> +	close(dir);
> +
> +	status_substr = strstr(str, power_gate_status);
> +	while (status_substr) {
> +		igt_assert_f((strncmp(status_substr + strlen(power_gate_status), expected_status,
> +				      strlen(expected_status)) == 0),
> +			      "Power Gate Status Should be %s\n %s\n", expected_status, str);
> +	status_substr = strstr(status_substr + strlen(power_gate_status), power_gate_status);
Indentation
> +	}
> +}
> +
> +static void cpg_basic(int fd, int gt)
> +{
> +	cpg_enabled(fd, gt);
> +	igt_system_suspend_autoresume(SUSPEND_STATE_S3, SUSPEND_TEST_NONE);
> +	cpg_enabled(fd, gt);
> +}
> +
> +static void cpg_gt_toggle(int fd)
> +{
> +	int gt;
> +
> +	fw_handle = igt_debugfs_open(fd, "forcewake_all", O_RDONLY);
> +	igt_assert_lte(0, fw_handle);
> +
> +	xe_for_each_gt(fd, gt)
> +		cpg_enabled(fd, gt);
> +
> +	xe_for_each_gt(fd, gt)
> +		powergate_status(fd, gt, "up");
add under the previous xe_for_each_gt

Thanks
Riana
> +
> +	close(fw_handle);
> +	sleep(1);
> +	xe_for_each_gt(fd, gt)
> +		powergate_status(fd, gt, "down");
> +}
> +
>   igt_main
>   {
>   	uint32_t d3cold_allowed;
> @@ -380,6 +461,17 @@ igt_main
>   		toggle_gt_c6(fd, NUM_REPS);
>   	}
>   
> +	igt_describe("Validate Coarse power gating status with S3 cycle");
> +	igt_subtest("cpg-basic")
> +		xe_for_each_gt(fd, gt)
> +			cpg_basic(fd, gt);
> +
> +	igt_describe("Toggle GT coarse power gating states by managing forcewake");
> +	igt_subtest("cpg-gt-toggle") {
> +		igt_install_exit_handler(close_fw_handle);
> +		cpg_gt_toggle(fd);
> +	}
> +
>   	igt_fixture {
>   		close(fd);
>   	}

  reply	other threads:[~2024-10-22  9:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21  7:19 [i-g-t, v3, 0/2] tests/xe: Add tests to validate GT coarse power gating status and toggle coarse power gating states sk.anirban
2024-10-21  7:19 ` [i-g-t, v3, 1/2] tests/intel/xe_pm_residency: Add GT coarse power gating validation sk.anirban
2024-10-22  9:50   ` Riana Tauro [this message]
2024-10-21  7:19 ` [i-g-t, v3, 2/2] HAX: Add Coarse power gating tests to fast feedback list sk.anirban
2024-10-21  8:11 ` ✓ Fi.CI.BAT: success for tests/xe: Add tests to validate GT coarse power gating status and toggle coarse power gating states (rev4) Patchwork
2024-10-21  8:19 ` ✗ CI.xeBAT: failure " Patchwork
2024-10-21  9:55 ` ✗ CI.xeFULL: " Patchwork
2024-10-21 10:20 ` ✓ Fi.CI.IGT: success " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2024-10-21  9:00 [i-g-t, v3, 0/2] tests/xe: Add tests to validate GT coarse power gating status and toggle coarse power gating states Sk Anirban
2024-10-21  9:00 ` [i-g-t, v3, 1/2] tests/intel/xe_pm_residency: Add GT coarse power gating validation Sk Anirban

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=44bce885-d0bf-4186-b8a6-9ff2acc86dfc@intel.com \
    --to=riana.tauro@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=sk.anirban@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