On Thu, Dec 12, 2013 at 10:59:03AM +, Chris Wilson wrote:
> On Fri, Dec 06, 2013 at 02:11:24PM -0800, Ben Widawsky wrote:
> > This is primarily a band aid for an unexplainable error in
> > gem_reloc_vs_gpu/forked-faulting-reloc-thrashing. Essentially as soon as
> > a relocated buffer (which had
On Fri, Dec 06, 2013 at 02:11:24PM -0800, Ben Widawsky wrote:
> This is primarily a band aid for an unexplainable error in
> gem_reloc_vs_gpu/forked-faulting-reloc-thrashing. Essentially as soon as
> a relocated buffer (which had a non-zero presumed offset) moved to
> offset 0, something goes bad.
This is primarily a band aid for an unexplainable error in
gem_reloc_vs_gpu/forked-faulting-reloc-thrashing. Essentially as soon as
a relocated buffer (which had a non-zero presumed offset) moved to
offset 0, something goes bad. Since I have been unable to solve this,
and potentially this is a good
This is primarily a band aid for an unexplainable error in
gem_reloc_vs_gpu/forked-faulting-reloc-thrashing. Essentially as soon as
a relocated buffer (which had a non-zero presumed offset) moved to
offset 0, something goes bad. Since I have been unable to solve this,
and potentially this is a good
