From: Steven Price <steven.price@arm.com>
To: Luben Tuikov <luben.tuikov@amd.com>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Cc: "Andrey Grodzovsky" <Andrey.Grodzovsky@amd.com>,
"kernel test robot" <lkp@intel.com>,
"Tomeu Vizoso" <tomeu.vizoso@collabora.com>,
"Rob Herring" <robh@kernel.org>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Alyssa Rosenzweig" <alyssa.rosenzweig@collabora.com>,
"Eric Anholt" <eric@anholt.net>,
"Christian Gmeiner" <christian.gmeiner@gmail.com>,
"Qiang Yu" <yuq825@gmail.com>,
"Russell King" <linux+etnaviv@armlinux.org.uk>,
"Alexander Deucher" <Alexander.Deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Lucas Stach" <l.stach@pengutronix.de>
Subject: Re: [PATCH 1/1] drm/scheduler: Job timeout handler returns status (v3)
Date: Thu, 21 Jan 2021 14:02:08 +0000 [thread overview]
Message-ID: <6d9e3d9d-e513-b2f0-9447-243c40e218cb@arm.com> (raw)
In-Reply-To: <20210120200959.163533-2-luben.tuikov@amd.com>
On 20/01/2021 20:09, Luben Tuikov wrote:
> This patch does not change current behaviour.
>
> The driver's job timeout handler now returns
> status indicating back to the DRM layer whether
> the device (GPU) is no longer available, such as
> after it's been unplugged, or whether all is
> normal, i.e. current behaviour.
>
> All drivers which make use of the
> drm_sched_backend_ops' .timedout_job() callback
> have been accordingly renamed and return the
> would've-been default value of
> DRM_GPU_SCHED_STAT_NOMINAL to restart the task's
> timeout timer--this is the old behaviour, and is
> preserved by this patch.
>
> v2: Use enum as the status of a driver's job
> timeout callback method.
>
> v3: Return scheduler/device information, rather
> than task information.
>
> Cc: Alexander Deucher <Alexander.Deucher@amd.com>
> Cc: Andrey Grodzovsky <Andrey.Grodzovsky@amd.com>
> Cc: Christian König <christian.koenig@amd.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Lucas Stach <l.stach@pengutronix.de>
> Cc: Russell King <linux+etnaviv@armlinux.org.uk>
> Cc: Christian Gmeiner <christian.gmeiner@gmail.com>
> Cc: Qiang Yu <yuq825@gmail.com>
> Cc: Rob Herring <robh@kernel.org>
> Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>
> Cc: Steven Price <steven.price@arm.com>
> Cc: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
> Cc: Eric Anholt <eric@anholt.net>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Luben Tuikov <luben.tuikov@amd.com>
Acked-by: Steven Price <steven.price@arm.com>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2021-01-21 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 20:09 [PATCH 0/1] Timeout handler now returns a value Luben Tuikov
2021-01-20 20:09 ` [PATCH 1/1] drm/scheduler: Job timeout handler returns status (v3) Luben Tuikov
2021-01-20 20:47 ` Alyssa Rosenzweig
2021-01-21 10:43 ` Christian König
2021-01-21 14:02 ` Steven Price [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=6d9e3d9d-e513-b2f0-9447-243c40e218cb@arm.com \
--to=steven.price@arm.com \
--cc=Alexander.Deucher@amd.com \
--cc=Andrey.Grodzovsky@amd.com \
--cc=alyssa.rosenzweig@collabora.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.gmeiner@gmail.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=l.stach@pengutronix.de \
--cc=linux+etnaviv@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=luben.tuikov@amd.com \
--cc=robh@kernel.org \
--cc=tomeu.vizoso@collabora.com \
--cc=yuq825@gmail.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