From: Pekka Paalanen <ppaalanen@gmail.com>
To: "André Almeida" <andrealmeid@igalia.com>
Cc: "Marek Olšák" <maraeo@gmail.com>,
pierre-eric.pelloux-prayer@amd.com,
"Sebastian Wick" <sebastian.wick@redhat.com>,
"Michel Dänzer" <michel.daenzer@mailbox.org>,
amd-gfx@lists.freedesktop.org,
"Timur Kristóf" <timur.kristof@gmail.com>,
"Randy Dunlap" <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
alexander.deucher@amd.com,
"Samuel Pitoiset" <samuel.pitoiset@gmail.com>,
kernel-dev@igalia.com, christian.koenig@amd.com
Subject: Re: [PATCH v5 1/1] drm/doc: Document DRM device reset expectations
Date: Tue, 4 Jul 2023 10:42:56 +0300 [thread overview]
Message-ID: <20230704104256.658b259d@eldfell> (raw)
In-Reply-To: <cedc57a5-779a-3ec6-cfbd-f51dfb17f2dc@igalia.com>
[-- Attachment #1: Type: text/plain, Size: 1394 bytes --]
On Mon, 3 Jul 2023 12:00:22 -0300
André Almeida <andrealmeid@igalia.com> wrote:
> Em 03/07/2023 05:49, Pekka Paalanen escreveu:
> > If an application freezes, that's "no problem"; the end user can just
> > continue using everything else. Alt-tab away etc. if the app was
> > fullscreen. I do that already with games on even Xorg.
> >
> > If a display server freezes, that's a desktop-wide problem, but so is
> > killing it.
> >
>
> Interesting, what GPU do you use? In my experience (AMD RX 5600 XT),
> hanging the GPU usually means that the rest of applications/compositor
> can't use the GPU either, freezing all user interactions. So killing the
> guilty app is one effective solution currently, but ignoring calls may
> help as well.
I don't know if what I'm seeing is a GPU hang or just e.g. Proton
getting somehow stuck, all I see is a game freezing. I just Alt+tab
back to Steam, force-stop it, and then all is fine again. This is how
it should work regardless of why a game freezes.
However, even if it was a GPU hang, if I am on a display server that
actually handles GPU resets, I don't see why the rest of the desktop
would not be able to recover. Individual apps are each to their own,
but at the very least non-GPU apps and the DE itself should not have
any problem (DE components can simply be restarted automatically).
Thanks,
pq
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-07-04 7:43 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 13:23 [PATCH v5 1/1] drm/doc: Document DRM device reset expectations André Almeida
2023-06-27 16:09 ` Randy Dunlap
2023-06-27 17:47 ` Christian König
2023-06-27 21:17 ` André Almeida
2023-06-29 13:11 ` André Almeida
[not found] ` <CAAxE2A4Hquz9bJNSEaUtBoJC3qbLBPYXd8i3JX9AhNUx_iUKpg@mail.gmail.com>
2023-06-27 21:31 ` André Almeida
2023-06-30 14:48 ` Sebastian Wick
2023-06-30 14:59 ` Alex Deucher
2023-06-30 15:11 ` Michel Dänzer
[not found] ` <CAAxE2A5C96k5ua+r938VA_+w7gHHNTdF3n8LwDb98W0Bf9wCVA@mail.gmail.com>
2023-07-03 7:12 ` Michel Dänzer
2023-07-03 8:49 ` Pekka Paalanen
2023-07-03 15:00 ` André Almeida
2023-07-04 7:42 ` Pekka Paalanen [this message]
[not found] ` <CAAxE2A7RGDY4eRC85CsqfszNzyKvMU2MX1wa+3HZ1hgNeAw3cQ@mail.gmail.com>
2023-07-04 2:38 ` Randy Dunlap
[not found] ` <CAAxE2A5UizddTTBWtuL480bDxgniVcBq7fjRGQhoC-5FG9vKpA@mail.gmail.com>
2023-07-04 2:48 ` Randy Dunlap
2023-07-04 7:54 ` Michel Dänzer
[not found] ` <CAAxE2A7tNCWkL_M2YcE=RN+nqqcokgBR4hcD2sR3fGAY2t4uLg@mail.gmail.com>
2023-07-05 7:32 ` Michel Dänzer
2023-07-05 15:53 ` Marek Olšák
2023-06-30 15:21 ` Sebastian Wick
2023-07-25 2:55 ` Non-robust apps and resets (was Re: [PATCH v5 1/1] drm/doc: Document DRM device reset expectations) André Almeida
2023-07-25 7:02 ` Simon Ser
2023-07-25 8:03 ` Michel Dänzer
2023-07-25 13:02 ` André Almeida
2023-07-26 8:07 ` Michel Dänzer
2023-08-02 7:38 ` Marek Olšák
2023-08-02 8:34 ` Michel Dänzer
2023-07-25 15:05 ` Marek Olšák
2023-07-25 17:00 ` Michel Dänzer
2023-07-26 7:55 ` Timur Kristóf
2023-08-04 13:03 ` [PATCH v5 1/1] drm/doc: Document DRM device reset expectations Daniel Vetter
2023-08-08 12:13 ` Sebastian Wick
2023-08-08 17:03 ` Marek Olšák
2023-08-09 7:35 ` Michel Dänzer
2023-08-09 19:15 ` Marek Olšák
2023-08-10 7:33 ` 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=20230704104256.658b259d@eldfell \
--to=ppaalanen@gmail.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=michel.daenzer@mailbox.org \
--cc=pierre-eric.pelloux-prayer@amd.com \
--cc=rdunlap@infradead.org \
--cc=samuel.pitoiset@gmail.com \
--cc=sebastian.wick@redhat.com \
--cc=timur.kristof@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