All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Peres <martin.peres-GANU6spQydw@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Marcin Slusarz
	<marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v2 4/4] drm/nouveau: gpu lockup recovery
Date: Wed, 02 May 2012 15:33:56 +0200	[thread overview]
Message-ID: <4FA137C4.3000900@free.fr> (raw)
In-Reply-To: <1335958137.1898.6.camel@nisroch>

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 related to this pending (basically,
> making the various driver subsystems more independent), which should be
> ready soon.  This'll go a long way to making it very easy to reset a
> single engine, and likely result in *far* faster recovery from hangs.
Hey,

What about kicking a channel that put the card in a bad state? Wouldn't 
that be possible?

This way, we don't loose the context of other channels and only the 
application that hang the card will be exited.

I wonder how pfifo handles commands sent to a non-existing channel, but 
I'm sure it shouldn't hang or anything.

Anyway, if this is not possible to only kick one channel, then what 
about kicking all channels, rePOSTING the card and using KMS to output 
the lockup report (and send a notification of the report through udev 
and store the report in a sysfs file)?

Let's not try to be perfect, let us just be able to do better bug reports.

Martin

  reply	other threads:[~2012-05-02 13:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25 21:20 [PATCH v2 4/4] drm/nouveau: gpu lockup recovery Marcin Slusarz
2012-04-25 21:32 ` Marcin Slusarz
     [not found] ` <1335388836-13127-4-git-send-email-marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-04-26  7:32   ` Ben Skeggs
2012-04-28 14:49     ` Marcin Slusarz
     [not found]       ` <20120428144956.GA10116-OI9uyE9O0yo@public.gmane.org>
2012-05-02 11:28         ` Ben Skeggs
2012-05-02 13:33           ` Martin Peres [this message]
     [not found]             ` <4FA137C4.3000900-GANU6spQydw@public.gmane.org>
2012-05-02 13:48               ` Ben Skeggs
2012-05-02 13:53                 ` Martin Peres
2012-04-28 14:56   ` Marcin Slusarz
     [not found]     ` <20120428145615.GB10116-OI9uyE9O0yo@public.gmane.org>
2012-04-30  9:47       ` Martin Peres
2012-05-27 19:52   ` Marcin Slusarz
2012-08-05 21:15   ` Marcin Slusarz

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=4FA137C4.3000900@free.fr \
    --to=martin.peres-ganu6spqydw@public.gmane.org \
    --cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=marcin.slusarz-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.