Nouveau Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair Popple <apopple-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: Alistair Popple <apopple-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: [PATCH 0/5] Improve Robust Channel (RC) recovery for Turing
Date: Fri, 30 Oct 2020 13:36:40 +1100	[thread overview]
Message-ID: <20201030023645.10114-1-apopple@nvidia.com> (raw)

This is an initial series of patches to improve channel recovery on Turing GPUs
with the goal of improving reliability enough to eventually enable SVM for
Turing. It's likely follow up patches will be required to fully address problems
with less trivial workloads than what I have been able to test thus far.

This series primarily addresses a number of hardware changes to interrupt layout
and channel recovery for Turing and for simple cases improves handling and
reliability of recovery.

I have been testing trivial OpenCL workloads and with this series have been able
to recover from while(1) style GPU loops and bad pointer dereferences on a
Turing GPU. However if there are less trivial tests available that have been
known to cause problems with channel recovery in the past let me know and I'll
start testing those as well.

Alistair Popple (5):
  drm/nouveau: Fix MMU fault interrupts on Turing
  drm/nouveau: Remove Turing interrupt hack
  drm/nouveau: Move Turing specific FIFO functions
  drm/nouveau: FIFO interrupt fixes for Turing
  drm/nouveau: Turing channel preemption fix

 .../gpu/drm/nouveau/nvkm/engine/fifo/gk104.c  |  46 +--
 .../gpu/drm/nouveau/nvkm/engine/fifo/gk104.h  |  32 ++
 .../gpu/drm/nouveau/nvkm/engine/fifo/tu102.c  | 364 +++++++++++++++++-
 .../gpu/drm/nouveau/nvkm/subdev/fault/tu102.c |  21 +-
 drivers/gpu/drm/nouveau/nvkm/subdev/mc/base.c |   3 -
 drivers/gpu/drm/nouveau/nvkm/subdev/mc/priv.h |   1 -
 .../gpu/drm/nouveau/nvkm/subdev/mc/tu102.c    | 113 +++++-
 7 files changed, 529 insertions(+), 51 deletions(-)

-- 
2.20.1

             reply	other threads:[~2020-10-30  2:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30  2:36 Alistair Popple [this message]
     [not found] ` <20201030023645.10114-1-apopple-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2020-10-30  2:36   ` [PATCH 1/5] drm/nouveau: Fix MMU fault interrupts on Turing Alistair Popple
2020-10-30  2:36   ` [PATCH 2/5] drm/nouveau: Remove Turing interrupt hack Alistair Popple
2020-10-30  2:36   ` [PATCH 3/5] drm/nouveau: Move Turing specific FIFO functions Alistair Popple
2020-10-30  2:36   ` [PATCH 4/5] drm/nouveau: FIFO interrupt fixes for Turing Alistair Popple
2020-10-30  2:36   ` [PATCH 5/5] drm/nouveau: Turing channel preemption fix Alistair Popple
2020-10-30 12:49   ` [PATCH 0/5] Improve Robust Channel (RC) recovery for Turing Karol Herbst

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=20201030023645.10114-1-apopple@nvidia.com \
    --to=apopple-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
    --cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /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