On Mon, Mar 01, 2010 at 04:00:02PM +1000, Dave Airlie wrote:
On Mon, Mar 1, 2010 at 2:47 AM, Jerome Glisse jgli...@redhat.com wrote:
On Sun, Feb 28, 2010 at 12:22:52PM +, Alan Swanson wrote:
On Fri, 2010-02-26 at 15:49 +0100, Jerome Glisse wrote:
This patch cleanup the fence code, it
On Fri, 2010-02-26 at 15:49 +0100, Jerome Glisse wrote:
This patch cleanup the fence code, it drops the timeout field of
fence as the time to complete each IB is unpredictable and shouldn't
be bound.
The fence cleanup lead to GPU lockup detection improvement, this
patch introduce a
On Sun, Feb 28, 2010 at 12:22:52PM +, Alan Swanson wrote:
On Fri, 2010-02-26 at 15:49 +0100, Jerome Glisse wrote:
This patch cleanup the fence code, it drops the timeout field of
fence as the time to complete each IB is unpredictable and shouldn't
be bound.
The fence cleanup lead
On Mon, Mar 1, 2010 at 2:47 AM, Jerome Glisse jgli...@redhat.com wrote:
On Sun, Feb 28, 2010 at 12:22:52PM +, Alan Swanson wrote:
On Fri, 2010-02-26 at 15:49 +0100, Jerome Glisse wrote:
This patch cleanup the fence code, it drops the timeout field of
fence as the time to complete each IB
This patch cleanup the fence code, it drops the timeout field of
fence as the time to complete each IB is unpredictable and shouldn't
be bound.
The fence cleanup lead to GPU lockup detection improvement, this
patch introduce a callback, allowing to do asic specific test for
lockup detection. In
2010/2/26 Jerome Glisse jgli...@redhat.com:
The fence cleanup lead to GPU lockup detection improvement, this
patch introduce a callback, allowing to do asic specific test for
lockup detection. In this patch the CP is use as a first indicator
of GPU lockup. If CP doesn't make progress during
