From: Alexandre Courbot <acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Eric Biggers <ebiggers3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [PATCH] fifo/gk104: kick channel upon removal
Date: Tue, 1 Mar 2016 16:59:05 +0900 [thread overview]
Message-ID: <1456819145-3141-1-git-send-email-acourbot@nvidia.com> (raw)
A channel may still be processed by the PBDMA even after removal, unless
it is properly kicked. Some chips are more sensible to this than others,
with GM20B triggering the issue very easily (the PBDMA will try to fetch
methods from the previously-removed channel after a new one is added).
Make sure this cannot happen by kicking the channel right after it is
disabled, and before the new runlist is submitted.
Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
---
Second attempt at this - the first version was reverted after causing a
regression: https://lists.freedesktop.org/archives/nouveau/2015-August/021842.html
I am pretty confident this one will pass though: we are now kicking the channel
only if it has a chance of being scheduled at that time, and in a path from which
we *will* access the FIFO registers after the kick, so if nothing complained until
then, kicking the channel should be unconsequential.
Eric, since you reported the regression on the first version, would you mind trying
this one and giving us your Tested-by? I have tested it on dGPU but unfortunately
could not set it up in an optimus-like manner, with power management kicking in.
drm/nouveau/nvkm/engine/fifo/gpfifogk104.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drm/nouveau/nvkm/engine/fifo/gpfifogk104.c b/drm/nouveau/nvkm/engine/fifo/gpfifogk104.c
index 2e1df01bd928..8b4a5e01829c 100644
--- a/drm/nouveau/nvkm/engine/fifo/gpfifogk104.c
+++ b/drm/nouveau/nvkm/engine/fifo/gpfifogk104.c
@@ -154,6 +154,7 @@ gk104_fifo_gpfifo_fini(struct nvkm_fifo_chan *base)
if (!list_empty(&chan->head)) {
gk104_fifo_runlist_remove(fifo, chan);
nvkm_mask(device, 0x800004 + coff, 0x00000800, 0x00000800);
+ gk104_fifo_gpfifo_kick(chan);
gk104_fifo_runlist_commit(fifo, chan->engine);
}
--
2.7.2
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2016-03-01 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 7:59 Alexandre Courbot [this message]
[not found] ` <1456819145-3141-1-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-03-02 3:53 ` [PATCH] fifo/gk104: kick channel upon removal Eric Biggers
2016-03-02 9:07 ` Alexandre Courbot
[not found] ` <CAAVeFuLGtLK9=qsLf1PcRFrpxuxOTfH6xunb83LBbqqdNPuoQw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-07 2:10 ` Alexandre Courbot
[not found] ` <CAAVeFu+taWyad_Hes1VVjLiRojEVKiBgFfwiT_M_VL0AdbY2Nw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-07 2:32 ` Eric Biggers
2016-03-07 2:39 ` Alexandre Courbot
[not found] ` <CAAVeFuLo9SmOOP+MixSxhnO_GM_fJfRUXjhU-thPQQXdoJFeqQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-07 2:48 ` Eric Biggers
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=1456819145-3141-1-git-send-email-acourbot@nvidia.com \
--to=acourbot-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=ebiggers3-Re5JQEeQqe8AvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.