Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: <janga.rahul.kumar@intel.com>, <igt-dev@lists.freedesktop.org>,
	<ramadevi.gandi@intel.com>
Cc: <matthew.d.roper@intel.com>
Subject: Re: [PATCH i-g-t 2/3] tests/intel/xe_pm: Add mocs runtime suspend resume test
Date: Tue, 7 May 2024 15:12:59 +0530	[thread overview]
Message-ID: <0426a690-7c73-435c-b264-bac5422c9caf@intel.com> (raw)
In-Reply-To: <20240504130458.2102132-3-janga.rahul.kumar@intel.com>



On 04-05-2024 18:34, janga.rahul.kumar@intel.com wrote:
> From: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
> 
> Add test to check mocs values are retained over runtime
> suspend/resume.
> 
> Cc: Badal Nilawar <badal.nilawar@intel.com>
> Cc: Matt Roper <matthew.d.roper@intel.com>
> Signed-off-by: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
Reviewed-by: Badal Nilawar <badal.nilawar@intel.com>
> ---
>   tests/intel/xe_pm.c | 43 +++++++++++++++++++++++++++++++++++++++++++
>   1 file changed, 43 insertions(+)
> 
> diff --git a/tests/intel/xe_pm.c b/tests/intel/xe_pm.c
> index 51442537b..73fd57636 100644
> --- a/tests/intel/xe_pm.c
> +++ b/tests/intel/xe_pm.c
> @@ -609,6 +609,45 @@ static void test_mmap(device_t device, uint32_t placement, uint32_t flags)
>   	close(fw_handle);
>   }
>   
> +/**
> + * SUBTEST: mocs_suspend_resume
> + * Description:
> + *     Validate mocs register contents over suspend resume
> + *
> + * Functionality: mocs
> + * Run type: FULL
> + */
> +static void test_mocs_suspend_resume(device_t device)
> +{
> +	int gt;
> +
> +	xe_for_each_gt(device.fd_xe, gt) {
> +		char path[256];
> +
> +		// Mocs debugfs contents before and after suspend-resume
> +		char mocs_content_pre[4096], mocs_contents_post[4096];
> +
> +		sprintf(path, "gt%d/mocs", gt);
> +		igt_assert(igt_debugfs_exists(device.fd_xe, path, O_RDONLY));
> +		igt_debugfs_dump(device.fd_xe, path);
> +		igt_debugfs_read(device.fd_xe, path, mocs_content_pre);
> +
> +		fw_handle = igt_debugfs_open(device.fd_xe, "forcewake_all", O_RDONLY);
> +		igt_assert(fw_handle >= 0);
> +		igt_assert(igt_get_runtime_pm_status() == IGT_RUNTIME_PM_STATUS_ACTIVE);
> +
> +		/* Runtime suspend  */
> +		close(fw_handle);
> +		igt_assert(igt_wait_for_pm_status(IGT_RUNTIME_PM_STATUS_SUSPENDED));
> +
> +		igt_assert(igt_debugfs_exists(device.fd_xe, path, O_RDONLY));
> +		igt_debugfs_dump(device.fd_xe, path);
> +		igt_debugfs_read(device.fd_xe, path, mocs_contents_post);
> +
> +		igt_assert(strcmp(mocs_content_pre, mocs_contents_post) == 0);
> +	}
> +}
> +
>   igt_main
>   {
>   	struct drm_xe_engine_class_instance *hwe;
> @@ -767,6 +806,10 @@ igt_main
>   			dpms_on_off(device, DRM_MODE_DPMS_ON);
>   			igt_pm_set_autosuspend_delay(device.pci_xe, delay_ms);
>   		}
> +
> +		igt_subtest("mocs_suspend_resume")
> +			test_mocs_suspend_resume(device);
> +
>   	}
>   
>   	igt_fixture {

  reply	other threads:[~2024-05-07  9:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-04 13:04 [PATCH i-g-t v3 0/3] Add mocs tests janga.rahul.kumar
2024-05-04 13:04 ` [PATCH i-g-t 1/3] tests/intel/xe_debugfs: Extend gt test to check mocs entry janga.rahul.kumar
2024-05-04 13:04 ` [PATCH i-g-t 2/3] tests/intel/xe_pm: Add mocs runtime suspend resume test janga.rahul.kumar
2024-05-07  9:42   ` Nilawar, Badal [this message]
2024-05-04 13:04 ` [PATCH i-g-t 3/3] tests/intel/xe_pm: Add mocs S2-idle/S3/S4 " janga.rahul.kumar
2024-05-07  9:50   ` Nilawar, Badal
2024-05-07 12:42   ` Rodrigo Vivi
2024-05-04 13:42 ` ✓ Fi.CI.BAT: success for Add mocs tests (rev3) Patchwork
2024-05-04 13:45 ` ✓ CI.xeBAT: " Patchwork
2024-05-04 14:43 ` ✗ CI.xeFULL: failure " Patchwork
2024-05-04 14:48 ` ✓ Fi.CI.IGT: success " 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=0426a690-7c73-435c-b264-bac5422c9caf@intel.com \
    --to=badal.nilawar@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=janga.rahul.kumar@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=ramadevi.gandi@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