On Thu, May 15, 2014 at 02:15:44PM +, Mateo Lozano, Oscar wrote:
> > I've done a very cursory read of this, and my original comment from my
> > original high-level review on the internal list still stands: I'm freaked
> > out by how
> > invasive this is into the existing ring code. All the cha
> I've done a very cursory read of this, and my original comment from my
> original high-level review on the internal list still stands: I'm freaked out
> by how
> invasive this is into the existing ring code. All the changes in i915_dma.c
> look
> very suspicious, since that code is for the lega
On Fri, May 09, 2014 at 01:08:30PM +0100, oscar.ma...@intel.com wrote:
> From: Oscar Mateo
>
> For a description of this patchset, please check the previous cover letter
> [1].
>
> Together with this patchset, I'm also submitting an IGT test: gem_execlist
> [2].
>
> v2:
> - Use the same conte
From: Oscar Mateo
For a description of this patchset, please check the previous cover letter [1].
Together with this patchset, I'm also submitting an IGT test: gem_execlist [2].
v2:
- Use the same context struct for all the different engines (suggested by Brad
Volkin).
- Rename write_tail to s
