Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] xe_pm: Kill display for PM tests
Date: Mon, 3 Apr 2023 16:55:42 +0200	[thread overview]
Message-ID: <2679f33b-76b8-def3-388e-1187b630c921@linux.intel.com> (raw)
In-Reply-To: <20230403053724.kctv5urufyh7aono@zkempczy-mobl2>

[-- Attachment #1: Type: text/plain, Size: 3540 bytes --]

Hey,

On 2023-04-03 07:37, Zbigniew Kempczyński wrote:
> On Tue, Mar 28, 2023 at 02:40:43PM +0200, Maarten Lankhorst wrote:
>> Display keeps PM alive, do the minimal initialization to disable
>> display for the PM tests entirely.
> What's the reason of enforcing releasing display before starting PM
> tests? Looks like introducing testing gap.

It's the easiest fix, and display is irrelevant for those tests. The 
system will not go into

a lower power when display keeps it in a high power state by holding a 
PM reference

What do you think of the below test instead?

----------->8---------

diff --git a/tests/xe/xe_pm.c b/tests/xe/xe_pm.c
index 23b8246ed..f681e253a 100644
--- a/tests/xe/xe_pm.c
+++ b/tests/xe/xe_pm.c
@@ -341,6 +341,30 @@ NULL));
  		igt_assert(in_d3(device, d_state));
  }
  
+static void test_pipe(device_t device, igt_display_t *display, enum pipe pipe,
+		      igt_output_t *output, enum igt_acpi_d_state d_state)
+{
+	struct igt_fb fb;
+
+	igt_assert(in_d3(device, d_state));
+
+	/* Just for fun, set a scaled fb as primary so scaler is active too */
+	igt_create_fb(display->drm_fd, 640, 480, DRM_FORMAT_XRGB8888, DRM_FORMAT_MOD_LINEAR, &fb);
+
+	igt_assert(in_d3(device, d_state));
+
+	igt_display_reset(display);
+	igt_output_set_pipe(output, pipe);
+	igt_plane_set_fb(igt_output_get_plane_type(output, DRM_PLANE_TYPE_PRIMARY), &fb);
+	igt_display_commit2(display, COMMIT_ATOMIC);
+	igt_assert(out_of_d3(device, d_state));
+
+	igt_display_reset(display);
+	igt_display_commit2(display, COMMIT_ATOMIC);
+	igt_remove_fb(display->drm_fd, &fb);
+	igt_assert(in_d3(device, d_state));
+}
+
  igt_main
  {
  	struct drm_xe_engine_class_instance *hwe;
@@ -363,19 +387,34 @@ igt_main
  		{ "d3cold", IGT_ACPI_D3Cold },
  		{ NULL },
  	};
+	enum pipe pipe;
+	igt_display_t display;
  
  	igt_fixture {
+		drmModeResPtr res;
+
  		memset(&device, 0, sizeof(device));
-		device.fd_xe = drm_open_driver(DRIVER_XE);
+		device.fd_xe = drm_open_driver_master(DRIVER_XE);
  		device.pci_xe = igt_device_get_pci_device(device.fd_xe);
  		device.pci_root = igt_device_get_pci_root_port(device.fd_xe);
  
+		kmstest_set_vt_graphics_mode();
  		xe_device_get(device.fd_xe);
  
  		/* Always perform initial once-basic exec checking for health */
  		xe_for_each_hw_engine(device.fd_xe, hwe)
  			test_exec(device, hwe, 1, 1, NO_SUSPEND, NO_RPM);
  
+		/* Kill display, if it exists */
+		res = drmModeGetResources(device.fd_xe);
+		if (res) {
+			drmModeFreeResources(res);
+			igt_display_require(&display, device.fd_xe);
+			igt_display_commit2(&display, COMMIT_ATOMIC);
+		} else {
+			display.drm_fd = -1;
+		}
+
  		get_d3cold_allowed(device.pci_xe, d3cold_allowed);
  		igt_assert(igt_setup_runtime_pm(device.fd_xe));
  	}
@@ -435,11 +474,31 @@ igt_main
  				test_exec(device, hwe, 16, 32,
  					  NO_SUSPEND, d->state);
  		}
+
+		for_each_pipe_static(pipe) {
+			igt_subtest_f("%s-pipe-%s", d->name, kmstest_pipe_name(pipe)) {
+				igt_output_t *output;
+				bool valid_output = false;
+
+				igt_require(display.drm_fd != -1);
+				igt_require_pipe(&display, pipe);
+				igt_assert(setup_d3(device, d->state));
+
+				for_each_valid_output_on_pipe(&display, pipe, output)
+					test_pipe(device, &display, pipe, output, d->state);
+
+				igt_require(valid_output);
+			}
+		}
  	}
  
  	igt_fixture {
  		set_d3cold_allowed(device.pci_xe, d3cold_allowed);
  		igt_restore_runtime_pm();
+
+		if (display.drm_fd != -1)
+			igt_display_fini(&display);
+
  		xe_device_put(device.fd_xe);
  		close(device.fd_xe);
  	}

[-- Attachment #2: Type: text/html, Size: 4125 bytes --]

  reply	other threads:[~2023-04-03 14:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 12:40 [igt-dev] [PATCH i-g-t 1/2] xe_pm: Kill display for PM tests Maarten Lankhorst
2023-03-28 12:40 ` [igt-dev] [PATCH i-g-t 2/2] tests/xe: Prepare for widening drm_xe_sync.handle to 64-bits Maarten Lankhorst
2023-04-03  5:58   ` Zbigniew Kempczyński
2023-03-28 13:27 ` [igt-dev] ✗ GitLab.Pipeline: warning for series starting with [i-g-t,1/2] xe_pm: Kill display for PM tests Patchwork
2023-03-28 13:42 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-03-28 23:53 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-04-03  5:37 ` [igt-dev] [PATCH i-g-t 1/2] " Zbigniew Kempczyński
2023-04-03 14:55   ` Maarten Lankhorst [this message]
2023-04-03 18:32 ` [igt-dev] ✗ Fi.CI.BUILD: failure for series starting with [i-g-t,1/2] xe_pm: Kill display for PM tests (rev2) 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=2679f33b-76b8-def3-388e-1187b630c921@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=zbigniew.kempczynski@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