Re: [Intel-gfx] [PATCH v3 2/2] drm/i915/gtt: Avoid using addresses in non-canonical form.

2015-09-23 Thread Daniel Vetter
On Thu, Sep 17, 2015 at 05:17:24PM +, Winiarski, Michal wrote: > On śro, 2015-09-16 at 11:50 +0200, Michał Winiarski wrote: > > According to bspec, some parts of HW expect the addresses to be in > > a canonical form where bits [63:48] == [47]. > > If we're using 32b addressing, we never need to

Re: [Intel-gfx] [PATCH v3 2/2] drm/i915/gtt: Avoid using addresses in non-canonical form.

2015-09-17 Thread Winiarski, Michal
On śro, 2015-09-16 at 11:50 +0200, Michał Winiarski wrote: > According to bspec, some parts of HW expect the addresses to be in > a canonical form where bits [63:48] == [47]. > If we're using 32b addressing, we never need to handle such high > addresses, but since we've recently added 48b address s

Re: [Intel-gfx] [PATCH v3 2/2] drm/i915/gtt: Avoid using addresses in non-canonical form.

2015-09-16 Thread Chris Wilson
On Wed, Sep 16, 2015 at 11:50:50AM +0200, Michał Winiarski wrote: > According to bspec, some parts of HW expect the addresses to be in > a canonical form where bits [63:48] == [47]. > If we're using 32b addressing, we never need to handle such high > addresses, but since we've recently added 48b ad

[Intel-gfx] [PATCH v3 2/2] drm/i915/gtt: Avoid using addresses in non-canonical form.

2015-09-16 Thread Michał Winiarski
According to bspec, some parts of HW expect the addresses to be in a canonical form where bits [63:48] == [47]. If we're using 32b addressing, we never need to handle such high addresses, but since we've recently added 48b address space support, lets satisfy the HW by converting the address prior t