On Tue, Apr 26, 2016 at 09:06:00AM +0100, Dave Gordon wrote:
> On 25/04/16 16:48, Chris Wilson wrote:
> >On Mon, Apr 25, 2016 at 04:21:58PM +0100, Dave Gordon wrote:
> >>On 24/04/16 19:10, Chris Wilson wrote:
> >>>Rather than reuse the current location of the context in the global GTT
> >>>for its
On 25/04/16 16:48, Chris Wilson wrote:
On Mon, Apr 25, 2016 at 04:21:58PM +0100, Dave Gordon wrote:
On 24/04/16 19:10, Chris Wilson wrote:
Rather than reuse the current location of the context in the global GTT
for its hardware identifier, use the context's unique ID assigned to it
for its
On Mon, Apr 25, 2016 at 04:21:58PM +0100, Dave Gordon wrote:
> On 24/04/16 19:10, Chris Wilson wrote:
> >Rather than reuse the current location of the context in the global GTT
> >for its hardware identifier, use the context's unique ID assigned to it
> >for its whole lifetime.
> >
>
On 24/04/16 19:10, Chris Wilson wrote:
Rather than reuse the current location of the context in the global GTT
for its hardware identifier, use the context's unique ID assigned to it
for its whole lifetime.
Signed-off-by: Chris Wilson
Reviewed-by: Tvrtko Ursulin
Rather than reuse the current location of the context in the global GTT
for its hardware identifier, use the context's unique ID assigned to it
for its whole lifetime.
Signed-off-by: Chris Wilson
Reviewed-by: Tvrtko Ursulin
---