Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Sundaresan, Sujaritha" <sujaritha.sundaresan@intel.com>
To: "Gupta, Anshuman" <anshuman.gupta@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [i-g-t] tests/intel: Add tests to run suspend without display
Date: Mon, 26 Feb 2024 08:51:01 +0530	[thread overview]
Message-ID: <3cc2055d-7ffe-41ad-8d55-40873373be44@intel.com> (raw)
In-Reply-To: <42bccfef-c5e1-48cd-a6ce-9f3bdc1efd30@intel.com>


On 2/22/2024 12:49 PM, Sundaresan, Sujaritha wrote:
>
> On 2/22/2024 12:33 PM, Gupta, Anshuman wrote:
>>
>>> -----Original Message-----
>>> From: Sundaresan, Sujaritha <sujaritha.sundaresan@intel.com>
>>> Sent: Thursday, February 22, 2024 12:26 PM
>>> To: igt-dev@lists.freedesktop.org
>>> Cc: Gupta, Anshuman <anshuman.gupta@intel.com>
>>> Subject: Re: [i-g-t] tests/intel: Add tests to run suspend without 
>>> display
>>>
>>> Hi all,
>>>
>>> As a heads up to those reviewing the patch, the pre-merge testing 
>>> for the
>>> added subtests is likely to fail due to a known sporadic issue with 
>>> unloading
>>> and reloading the driver with no display.
>>>
>>> Thanks,
>>>
>>> Suja
>>>
>>> On 2/22/2024 12:36 PM, 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.
>>>>
>>>> Signed-off-by: Sujaritha Sundaresan <sujaritha.sundaresan@intel.com>
>>>> ---
>>>>    tests/intel/xe_pm.c | 22 ++++++++++++++++++++++
>>>>    1 file changed, 22 insertions(+)
>>>>
>>>> diff --git a/tests/intel/xe_pm.c b/tests/intel/xe_pm.c index
>>>> a0045da0b..e94835f0d 100644
>>>> --- a/tests/intel/xe_pm.c
>>>> +++ b/tests/intel/xe_pm.c
>>>> @@ -16,6 +16,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"
>>>> @@ -236,6 +237,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
>>>> @@ -618,6 +623,23 @@ igt_main
>>>>                          NO_RPM);
>>>>            }
>>>>
>>>> +        igt_subtest_f("%s-without-display", s->name) {
>>>> +
>>>> +            if (!drmModeGetResources(device.fd_xe))
>>>> +                return;
>>>> +
>>>> +            xe_for_each_engine(device.fd_xe, hwe) {
>>>> +                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);
>>>> +
>>>> +                test_exec(device, hwe, 1, 2, s->state,
>>>> +                      NO_RPM);
>>>> +            }
>>>> +        }
>> We need to reload the driver with display as normal ?
>> Anshuman.
>
> Hmm maybe. That will need another unload and non-conditional re-load 
> cycle right ?
>
> Suja
>
Hi Anshuman,

Should I go ahead with the above change ?

Thanks,

Suja

>>>> +
>>>>            for (const struct d_state *d = d_states; d->name; d++) {
>>>>                igt_subtest_f("%s-%s-basic-exec", s->name, d->name)
>>> {
>>>> igt_assert(setup_d3(device, d->state));

  reply	other threads:[~2024-02-26  3:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22  7:06 [i-g-t] tests/intel: Add tests to run suspend without display Sujaritha Sundaresan
2024-02-22  6:55 ` Sundaresan, Sujaritha
2024-02-22  7:03   ` Gupta, Anshuman
2024-02-22  7:19     ` Sundaresan, Sujaritha
2024-02-26  3:21       ` Sundaresan, Sujaritha [this message]
2024-02-26  3:24         ` Gupta, Anshuman
2024-02-22  8:21 ` ✓ CI.xeBAT: success for " Patchwork
2024-02-22  8:39 ` ✓ Fi.CI.BAT: " Patchwork
2024-02-22 15:31 ` ✗ Fi.CI.IGT: failure " 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=3cc2055d-7ffe-41ad-8d55-40873373be44@intel.com \
    --to=sujaritha.sundaresan@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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