Hi
I refreshed this patchset to current nouveau git.
http://people.freedesktop.org/~mslusarz/gpu-lockup-recovery/
Marcin
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
From: Marcin Slusarz marcin.slus...@gmail.com
Subject: [PATCH v4] drm/nouveau: gpu lockup recovery
Detect lockups by watching for vm flush / fence timeouts and signal them by
returning EIO. When EIOs are met at ioctl level, reset the card and repeat
last ioctl.
GPU reset is done by going through
On Sat, 2012-04-28 at 16:49 +0200, Marcin Slusarz wrote:
On Thu, Apr 26, 2012 at 05:32:29PM +1000, Ben Skeggs wrote:
On Wed, 2012-04-25 at 23:20 +0200, Marcin Slusarz wrote:
Overall idea:
Detect lockups by watching for timeouts (vm flush / fence), return -EIOs,
handle them at ioctl
On 02/05/2012 13:28, Ben Skeggs wrote:
Right, again, I don't disagree :) I think we can improve a lot on the
big-hammer-suspend-the-gpu solution though, and instead reset only the
faulting engine. It's (in theory) almost possible for us to do now, but
I have a couple of reworks to areas
On Wed, 2012-05-02 at 15:33 +0200, Martin Peres wrote:
On 02/05/2012 13:28, Ben Skeggs wrote:
Right, again, I don't disagree :) I think we can improve a lot on the
big-hammer-suspend-the-gpu solution though, and instead reset only the
faulting engine. It's (in theory) almost possible for
On 02/05/2012 15:48, Ben Skeggs wrote:
On Wed, 2012-05-02 at 15:33 +0200, Martin Peres wrote:
On 02/05/2012 13:28, Ben Skeggs wrote:
Right, again, I don't disagree :) I think we can improve a lot on the
big-hammer-suspend-the-gpu solution though, and instead reset only the
faulting engine.
Le 28/04/2012 16:56, Marcin Slusarz a écrit :
On Wed, Apr 25, 2012 at 11:20:36PM +0200, Marcin Slusarz wrote:
Overall idea:
Detect lockups by watching for timeouts (vm flush / fence), return -EIOs,
handle them at ioctl level, reset the GPU and repeat last ioctl.
GPU reset is done by doing
On Thu, Apr 26, 2012 at 05:32:29PM +1000, Ben Skeggs wrote:
On Wed, 2012-04-25 at 23:20 +0200, Marcin Slusarz wrote:
Overall idea:
Detect lockups by watching for timeouts (vm flush / fence), return -EIOs,
handle them at ioctl level, reset the GPU and repeat last ioctl.
GPU reset is
On Wed, Apr 25, 2012 at 11:20:36PM +0200, Marcin Slusarz wrote:
Overall idea:
Detect lockups by watching for timeouts (vm flush / fence), return -EIOs,
handle them at ioctl level, reset the GPU and repeat last ioctl.
GPU reset is done by doing suspend / resume cycle with few tweaks:
-
On Wed, 2012-04-25 at 23:20 +0200, Marcin Slusarz wrote:
Overall idea:
Detect lockups by watching for timeouts (vm flush / fence), return -EIOs,
handle them at ioctl level, reset the GPU and repeat last ioctl.
GPU reset is done by doing suspend / resume cycle with few tweaks:
- CPU-only bo
Overall idea:
Detect lockups by watching for timeouts (vm flush / fence), return -EIOs,
handle them at ioctl level, reset the GPU and repeat last ioctl.
GPU reset is done by doing suspend / resume cycle with few tweaks:
- CPU-only bo eviction
- ignoring vm flush / fence timeouts
- shortening
On Wed, Apr 25, 2012 at 11:20:36PM +0200, Marcin Slusarz wrote:
Overall idea:
Detect lockups by watching for timeouts (vm flush / fence), return -EIOs,
handle them at ioctl level, reset the GPU and repeat last ioctl.
GPU reset is done by doing suspend / resume cycle with few tweaks:
-
12 matches
Mail list logo
