From: "Sundaresan, Sujaritha" <sujaritha.sundaresan@intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
<igt-dev@lists.freedesktop.org>, <anshuman.gupta@intel.com>,
<katarzyna.piecielska@intel.com>
Subject: Re: [PATCH i-g-t, v4] tests/intel/xe_pm: Add tests for suspend without display
Date: Tue, 27 Aug 2024 13:41:57 +0530 [thread overview]
Message-ID: <82a8af36-642a-4747-b085-924c02e6308e@intel.com> (raw)
In-Reply-To: <172468301865.6014.9946879676247551400@gjsousa-mobl2>
[-- Attachment #1: Type: text/plain, Size: 4064 bytes --]
On 8/26/2024 8:06 PM, Gustavo Sousa wrote:
> Quoting Lucas De Marchi (2024-08-22 18:01:19-03:00)
>> On Thu, Aug 22, 2024 at 02:45:15PM GMT, Gustavo Sousa wrote:
>>> Quoting Kamil Konieczny (2024-08-22 13:52:43-03:00)
>>>> Hi Sujaritha,
>>>> On 2024-08-22 at 14:50:58 +0530, Sujaritha Sundaresan wrote:
>>>>> Add tests to validate basic execution suspend/resume cycle
>>>>> without display module to rule out display related issues
>>>>> from the suspend/resume stack.
>>>>>
>>>>> v2: Add normal reload cycle after running test (Anshuman)
>>>>>
>>>>> v3: Rebase
>>>>>
>>>>> v4: Change commit name/header (Kamil)
>>>>>
>>>>> Signed-off-by: Sujaritha Sundaresan<sujaritha.sundaresan@intel.com>
>>>>> Acked-by: Katarzyna PiecielskaKatarzyna.piecielska@intel.com<Katarzyna.piecielska@intel.com>
>>>>> Reviewed-by: Anshuman Gupta<anshuman.gupta@intel.com>
>>>>> ---
>>>>> tests/intel/xe_pm.c | 34 ++++++++++++++++++++++++++++++++++
>>>>> 1 file changed, 34 insertions(+)
>>>>>
>>>>> diff --git a/tests/intel/xe_pm.c b/tests/intel/xe_pm.c
>>>>> index eee89428c..1623a56c7 100644
>>>>> --- a/tests/intel/xe_pm.c
>>>>> +++ b/tests/intel/xe_pm.c
>>>>> @@ -17,6 +17,7 @@
>>>>>
>>>>> #include "igt.h"
>>>>> #include "lib/igt_device.h"
>>>>> +#include "lib/igt_kmod.h"
>>>>> #include "lib/igt_pm.h"
>>>>> #include "lib/igt_sysfs.h"
>>>>> #include "lib/igt_syncobj.h"
>>>>> @@ -229,6 +230,10 @@ static void close_fw_handle(int sig)
>>>>> * Description: suspend/autoresume on %arg[1] state and exec after RPM
>>>>> * Functionality: pm - %arg[1]
>>>>> *
>>>>> + * SUBTEST: %s-without-display
>>>>> + * Description: suspend/autoresume on %arg[1] state without display
>>>>> + * Functionality: pm - %arg[1]
>>>>> + *
>>>>> * arg[1]:
>>>>> *
>>>>> * @s2idle: s2idle
>>>>> @@ -681,6 +686,7 @@ igt_main
>>>>> struct drm_xe_engine_class_instance *hwe;
>>>>> device_t device;
>>>>> uint32_t d3cold_allowed;
>>>>> + const char *opts;
>>>>> int sysfs_fd;
>>>>>
>>>>> const struct s_state {
>>>>> @@ -757,6 +763,34 @@ igt_main
>>>>> NO_RPM, 0);
>>>>> }
>>>>>
>>>>> + igt_subtest_f("%s-without-display", s->name) {
>>>>> +
>>>>> + if (!drmModeGetResources(device.fd_xe))
>>>>> + return;
>>>> This should be skip or save it (as global?) and run test on headless.
>>>>
>>>>> +
>>>>> + xe_for_each_engine(device.fd_xe, hwe) {
>>>>> +
>>>>> + igt_debug("Reload w/o display\n");
>>>>> +
>>>>> + igt_kmsg(KMSG_INFO "Unloading Xe\n");
>>>>> + igt_assert_eq(igt_xe_driver_unload(), 0);
>>>>> +
>>>>> + igt_kmsg(KMSG_INFO "Re-loading Xe without display\n");
>>>>> + igt_assert_eq(igt_xe_driver_load("enable_display=0"), 0);
>>>> This param was renamed to probe_display, see
>>>> https://patchwork.freedesktop.org/series/137096/
>>>> tests/intel/xe_module_load: Rename enable_display module param
>>>> Submitted by Lucas De Marchi on Aug. 9, 2024, 5:30 p.m.
>>>>
>>>> +Cc Lucas
>>> And disable_display=1 might be more appropriate, because probe_display
>>> would simply skip the probe for display?
>> Good point. For platforms with display, is it expected that suspend works
>> if DMC is not loaded? Otherwise we will actually have to touch display
>> to disable it to be allowed to suspend.
> Well, for s2idle (s0ix for intel), DC6 is required, which in turn
> requires the DMC.
>
> For s3, I'm not really sure what DC state would be required, but I would
> assume that we would need the driver to put the display in a low-power
> state, so disable_display=1 seems to be needed here. Someone with more
> experience could chime in to confirm this.
>
> --
> Gustavo Sousa
Is there someone else specific that can be brought into this
conversation to help answer these questions ?
Thanks,
Suja
[-- Attachment #2: Type: text/html, Size: 5424 bytes --]
next prev parent reply other threads:[~2024-08-27 8:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 9:20 [PATCH i-g-t, v4] tests/intel/xe_pm: Add tests for suspend without display Sujaritha Sundaresan
2024-08-22 10:07 ` ✓ CI.xeBAT: success for " Patchwork
2024-08-22 10:09 ` ✓ Fi.CI.BAT: " Patchwork
2024-08-22 14:36 ` ✗ CI.xeFULL: failure " Patchwork
2024-08-22 16:52 ` [PATCH i-g-t, v4] " Kamil Konieczny
2024-08-22 17:45 ` Gustavo Sousa
2024-08-22 21:01 ` Lucas De Marchi
2024-08-26 11:12 ` Sundaresan, Sujaritha
2024-08-26 13:57 ` Lucas De Marchi
2024-08-27 8:10 ` Sundaresan, Sujaritha
2024-08-26 14:36 ` Gustavo Sousa
2024-08-27 8:11 ` Sundaresan, Sujaritha [this message]
2024-08-27 9:29 ` Gupta, Anshuman
2024-08-27 12:48 ` Gustavo Sousa
[not found] ` <CY5PR11MB6211B873C18594896BD21FA295942@CY5PR11MB6211.namprd11.prod.outlook.com>
2024-08-28 8:46 ` Sundaresan, Sujaritha
2024-09-11 5:19 ` Sundaresan, Sujaritha
2024-09-11 15:10 ` Jani Nikula
2024-09-13 8:29 ` Sundaresan, Sujaritha
2024-09-23 9:30 ` Jani Nikula
2024-08-23 6:20 ` ✗ Fi.CI.IGT: failure 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=82a8af36-642a-4747-b085-924c02e6308e@intel.com \
--to=sujaritha.sundaresan@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=katarzyna.piecielska@intel.com \
--cc=lucas.demarchi@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