From: Dave Airlie <airlied@gmail.com>
To: Mike Mestnik <cheako911@yahoo.com>
Subject: Re: [BUG] r200 dri driver deadlocks
Date: Tue, 7 Sep 2004 16:54:27 +1000 [thread overview]
Message-ID: <21d7e99704090623544c6ecaf5@mail.gmail.com> (raw)
In-Reply-To: <20040907063442.3574.qmail@web11906.mail.yahoo.com>
> Dose the DRM varify that the cmds are in this order? Why not just have
> the DRM 'sort' the cmds? A simple bouble sort would have no more overhead
> then the check for correct order, but it would fix missordered cmd
> streams.
>
> Once this is done the statement holds true, userland stuff should never...
>
Feel free to implement it and profile it, but there are so many ways
to lock up a radeon chip it is scary, the above was just one example,
some days if you look at it funny it can lockup :-), it is accepted
that userland can crap out 3D chips, the Intel ones are fairly easy to
hangup also..
Dave.
next prev parent reply other threads:[~2004-09-07 6:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 9:16 [BUG] r200 dri driver deadlocks Patrick McFarland
2004-09-04 10:59 ` Dave Airlie
2004-09-05 8:40 ` Patrick McFarland
2004-09-04 18:14 ` Michel Dänzer
2004-09-04 20:36 ` Patrick McFarland
2004-09-05 6:34 ` Michel Dänzer
2004-09-05 8:22 ` Patrick McFarland
2004-09-05 17:40 ` Michel Dänzer
2004-09-05 20:18 ` Patrick McFarland
2004-09-05 20:25 ` Michel Dänzer
2004-09-05 21:47 ` Patrick McFarland
2004-09-06 0:14 ` Lee Revell
2004-09-06 10:51 ` Felix Kühling
2004-09-07 6:34 ` Mike Mestnik
2004-09-07 6:54 ` Dave Airlie [this message]
2004-09-07 7:06 ` Mike Mestnik
2004-09-07 9:40 ` Roland Scheidegger
2004-09-06 11:01 ` Patrick McFarland
2004-09-06 18:12 ` Michel Dänzer
2004-09-07 9:07 ` Patrick McFarland
2004-09-07 9:09 ` Patrick McFarland
2004-09-07 9:41 ` Alan Cox
2004-09-09 4:24 ` Alexander E. Patrakov
[not found] <21d7e997040907013071ebb60d@mail.gmail.com>
2004-09-08 4:13 ` Mike Mestnik
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=21d7e99704090623544c6ecaf5@mail.gmail.com \
--to=airlied@gmail.com \
--cc=cheako911@yahoo.com \
/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.