From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Wu, Hersen" <hersenxs.wu@amd.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"Mahfooz, Hamza" <Hamza.Mahfooz@amd.com>
Subject: Re: [igt-dev] [PATCH] [i-g-t] tests/amdgpu/amd_hotplug: add delay after igt_system_suspend_autoresume
Date: Mon, 24 Apr 2023 22:15:14 +0300 [thread overview]
Message-ID: <ZEbVQmgEpx2PMSIj@intel.com> (raw)
In-Reply-To: <PH8PR12MB69628ACAD108D765A888BBFBFD679@PH8PR12MB6962.namprd12.prod.outlook.com>
On Mon, Apr 24, 2023 at 07:02:04PM +0000, Wu, Hersen wrote:
> [AMD Official Use Only - General]
>
> After igt_system_suspend_autoresume is executed, Linux kernel should be out of sleep mode.
> By adding read power_state from /sys/class/drm/card0/device# cat power_state. Value is D0.
> This is already checked by reading amdgpu adev->in_suspend, value is false.
>
> Some other components may not finish process for resume.
>
> When batch run test case below,
>
> igt@amdgpu/amd_hotplug@basic-suspend
> igt@amdgpu/amd_link_settings@link-training-configs
> igt@amdgpu/amd_mem_leak@connector-suspend-resume
>
>
> igt@amdgpu/amd_hotplug@basic-suspend is executed, but the rest two test case are skipped.
>
> I do not find method to check if all SW components are out of resume processing. The delay 30 seconds is safe value based on experiments.
There is no such suspend processing. The kernel just freezed/thaws
userspace as a whole. Once the igt is running so is rest of userspace.
> AMD IGT test list are executed 15 loops.
>
> With delay 15 seconds, intermittent failure could still be captured.
>
> Thanks!
> Hersen
>
>
>
>
>
>
>
> -----Original Message-----
> From: Siqueira, Rodrigo <Rodrigo.Siqueira@amd.com>
> Sent: Monday, April 24, 2023 12:50 PM
> To: Wu, Hersen <hersenxs.wu@amd.com>; igt-dev@lists.freedesktop.org; Pillai, Aurabindo <Aurabindo.Pillai@amd.com>; Hung, Alex <Alex.Hung@amd.com>; Mahfooz, Hamza <Hamza.Mahfooz@amd.com>
> Subject: Re: [PATCH] [i-g-t] tests/amdgpu/amd_hotplug: add delay after igt_system_suspend_autoresume
>
>
>
> On 4/24/23 07:48, Hersen Wu wrote:
> > at call back of igt_system_suspend_autoresume, linux kernel resume
> > finish and in d0 state. but user mode components may not be fully out
> > of sleep mode. add delay wait for system stable before issuing
> > debugfs_hotplug_trigger.
> >
> > Signed-off-by: Hersen Wu <hersenxs.wu@amd.com>
> > ---
> > tests/amdgpu/amd_hotplug.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/tests/amdgpu/amd_hotplug.c b/tests/amdgpu/amd_hotplug.c
> > index 736040a2..1c946ff8 100644
> > --- a/tests/amdgpu/amd_hotplug.c
> > +++ b/tests/amdgpu/amd_hotplug.c
> > @@ -133,6 +133,7 @@ static void test_hotplug_basic(data_t *data, bool suspend)
> > if (suspend) {
> > igt_system_suspend_autoresume(SUSPEND_STATE_MEM,
> > SUSPEND_TEST_NONE);
> > + sleep(30);
>
> Do we need to wait all of this time? If so, why?
>
> > }
> >
> > /* Trigger hotplug and confirm reference image is the same. */
--
Ville Syrjälä
Intel
prev parent reply other threads:[~2023-04-24 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 13:48 [igt-dev] [PATCH] [i-g-t] tests/amdgpu/amd_hotplug: add delay after igt_system_suspend_autoresume Hersen Wu
2023-04-24 16:07 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2023-04-24 16:49 ` [igt-dev] [PATCH] [i-g-t] " Rodrigo Siqueira Jordao
2023-04-24 19:02 ` Wu, Hersen
2023-04-24 19:15 ` Ville Syrjälä [this message]
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=ZEbVQmgEpx2PMSIj@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=Hamza.Mahfooz@amd.com \
--cc=hersenxs.wu@amd.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