All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 18242] New: kernel should forbid app from using GPU if it causes lockups
Date: Sat, 11 Sep 2010 07:28:56 GMT	[thread overview]
Message-ID: <bug-18242-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=18242

           Summary: kernel should forbid app from using GPU if it causes
                    lockups
           Product: Drivers
           Version: 2.5
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: enhancement
          Priority: P1
         Component: Video(DRI - non Intel)
        AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
        ReportedBy: edwintorok@gmail.com
        Regression: No


During the testing of r600g (still in development) it happens that some mesa
demos/games lockup the GPU. 
Most of the time the kernel recovers from this nicely, however the app will
lockup the GPU over and over again.

It doesn't even know the correct process, for example it was the gloss demo
(using direct rendering) this time:
[ 3070.276433] GPU lockup (waiting for 0x0003708B last fence id 0x00037088)
...
[ 3070.276467] Pid: 4274, comm: Xorg Not tainted 2.6.36-rc3-phenom #96

It could have been an app using LIBGL_ALWAYS_INDIRECT=1 though, so just killing
the app causing the lockup is not a good idea (could easily lead to getting X
killed).

I think the kernel should forbid the app from sending any more GPU commands
(perhaps by returning failure for every ioctl it does?) once it determines it
locked up. So in this case it'd first forbid Xorg, then see there is another
lockup, then forbid gloss.
It should probably print a message like:
Process '<processname>' (pid <pid>) caused a GPU lockup, forbidding GPU
commands for 'N minutes'. To reenable do 'echo <pid>
>/sys/kernel/..../gpu_reenable'.



Of course it'd be best if the kernel wouldn't accept the GPU commands leading
to a GPU lockup, but that might not be possible to determine in general
(whether certain GPU instructions will cause a lockup or not).

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing
http://p.sf.net/sfu/novell-sfdev2dev
--

             reply	other threads:[~2010-09-11  7:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-11  7:28 bugzilla-daemon [this message]
2012-05-12 15:48 ` [Bug 18242] kernel should forbid app from using GPU if it causes lockups bugzilla-daemon
2012-05-12 15:49 ` bugzilla-daemon

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=bug-18242-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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.