[Intel-gfx] [PATCH 13/21] drm/i915: add support for 64K scratch page

2017-10-06 Thread Matthew Auld
Before we can fully enable 64K pages, we need to first support a 64K scratch page if we intend to support the case where we have object sizes < 2M, since any scratch PTE must also point to a 64K region. Without this our 64K usage is limited to objects which completely fill the page-table, and ther

[Intel-gfx] [PATCH 13/21] drm/i915: add support for 64K scratch page

2017-10-05 Thread Matthew Auld
Before we can fully enable 64K pages, we need to first support a 64K scratch page if we intend to support the case where we have object sizes < 2M, since any scratch PTE must also point to a 64K region. Without this our 64K usage is limited to objects which completely fill the page-table, and ther

[Intel-gfx] [PATCH 13/21] drm/i915: add support for 64K scratch page

2017-09-29 Thread Matthew Auld
Before we can fully enable 64K pages, we need to first support a 64K scratch page if we intend to support the case where we have object sizes < 2M, since any scratch PTE must also point to a 64K region. Without this our 64K usage is limited to objects which completely fill the page-table, and ther

Re: [Intel-gfx] [PATCH 13/21] drm/i915: add support for 64K scratch page

2017-09-23 Thread Chris Wilson
Quoting Matthew Auld (2017-09-22 18:32:44) > Before we can fully enable 64K pages, we need to first support a 64K > scratch page if we intend to support the case where we have object sizes > < 2M, since any scratch PTE must also point to a 64K region. Without > this our 64K usage is limited to obj

[Intel-gfx] [PATCH 13/21] drm/i915: add support for 64K scratch page

2017-09-22 Thread Matthew Auld
Before we can fully enable 64K pages, we need to first support a 64K scratch page if we intend to support the case where we have object sizes < 2M, since any scratch PTE must also point to a 64K region. Without this our 64K usage is limited to objects which completely fill the page-table, and ther