[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8e560379-4bdc-a3f0-591a-435833bfacda@mailbox.org>
Date: Mon, 14 Aug 2023 12:11:35 +0200
From: Michel Dänzer <michel.daenzer@...lbox.org>
To: André Almeida <andrealmeid@...lia.com>,
dri-devel@...ts.freedesktop.org, amd-gfx@...ts.freedesktop.org,
linux-kernel@...r.kernel.org
Cc: pierre-eric.pelloux-prayer@....com,
Randy Dunlap <rdunlap@...radead.org>,
'Marek Olšák' <maraeo@...il.com>,
Timur Kristóf <timur.kristof@...il.com>,
Pekka Paalanen <ppaalanen@...il.com>,
Samuel Pitoiset <samuel.pitoiset@...il.com>,
kernel-dev@...lia.com, alexander.deucher@....com,
christian.koenig@....com
Subject: Re: [PATCH v6] drm/doc: Document DRM device reset expectations
On 8/11/23 20:55, André Almeida wrote:
> Create a section that specifies how to deal with DRM device resets for
> kernel and userspace drivers.
>
> Signed-off-by: André Almeida <andrealmeid@...lia.com>
[...]
> +Robustness
> +----------
> +
> +The only way to try to keep an application working after a reset is if it
> +complies with the robustness aspects of the graphical API that it is using.
"The only way to try to keep a graphical API context working after a device reset [...]"
If a graphical API context stops working properly, it doesn't necessarily mean that the application as a whole stops working.
--
Earthling Michel Dänzer | https://redhat.com
Libre software enthusiast | Mesa and Xwayland developer
Powered by blists - more mailing lists