From: "Michel Dänzer" <michel.daenzer@mailbox.org>
To: "Marek Olšák" <maraeo@gmail.com>,
"Christian König" <christian.koenig@amd.com>
Cc: "Pierre-Eric Pelloux-Prayer" <pierre-eric.pelloux-prayer@amd.com>,
"André Almeida" <andrealmeid@igalia.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"amd-gfx mailing list" <amd-gfx@lists.freedesktop.org>,
"Tuikov, Luben" <Luben.Tuikov@amd.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
kernel-dev@igalia.com, "Deucher,
Alexander" <alexander.deucher@amd.com>
Subject: Re: [PATCH] drm/amdgpu: Mark contexts guilty for any reset type
Date: Tue, 25 Apr 2023 12:27:37 +0200 [thread overview]
Message-ID: <784561bb-0937-befc-3774-892d6f6a4318@mailbox.org> (raw)
In-Reply-To: <CAAxE2A6Soq28ACV-m1OzG8CA-_VWp+N2wapsABzm2Nda=Qe+yA@mail.gmail.com>
On 4/24/23 18:45, Marek Olšák wrote:
> Soft resets are fatal just as hard resets, but no reset is "always fatal". There are cases when apps keep working depending on which features are being used. It's still unsafe.
Agreed, in theory.
In practice, from a user PoV, right now there's pretty much 0 chance of the user session surviving if the GPU context in certain critical processes (e.g. the Wayland compositor or Xwayland) hits a fatal reset. There's a > 0 chance of it surviving after a soft reset. There's ongoing work towards making user-space components more robust against fatal resets, but it's taking time. Meanwhile, I suspect most users would take the > 0 chance.
--
Earthling Michel Dänzer | https://redhat.com
Libre software enthusiast | Mesa and Xwayland developer
next prev parent reply other threads:[~2023-04-25 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 1:43 André Almeida
2023-04-24 5:11 ` kernel test robot
2023-04-24 7:03 ` Christian König
2023-04-24 13:26 ` André Almeida
2023-04-24 15:27 ` Michel Dänzer
[not found] ` <CAAxE2A6Soq28ACV-m1OzG8CA-_VWp+N2wapsABzm2Nda=Qe+yA@mail.gmail.com>
2023-04-25 10:27 ` Michel Dänzer [this message]
[not found] ` <CAAxE2A6iuuVA7zjHM8YcTGMpEWuYV=hGRR1YW6W-qXHwAg9w7w@mail.gmail.com>
[not found] ` <19406ec5-79d6-e9e6-fbdd-eb2f4a872fc4@amd.com>
2023-04-25 12:14 ` Michel Dänzer
2023-04-25 12:44 ` Christian König
[not found] ` <CAAxE2A4capwpc40F49cgZBC9jJisODqNjTe0cM_pS7si5EkW3g@mail.gmail.com>
2023-04-26 9:51 ` Michel Dänzer
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=784561bb-0937-befc-3774-892d6f6a4318@mailbox.org \
--to=michel.daenzer@mailbox.org \
--cc=Luben.Tuikov@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrealmeid@igalia.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maraeo@gmail.com \
--cc=pierre-eric.pelloux-prayer@amd.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
all inboxes | Powered by JetHome®