On 2017.06.29 12:59:08 +0100, Chris Wilson wrote:
> Quoting Matthew Auld (2017-06-29 12:54:51)
> > On 29 June 2017 at 07:36, Zhenyu Wang wrote:
> > > We need to fallback to default supported page size when vGPU is active
> > > (intel_vgpu_active() is true).
> > >
Quoting Matthew Auld (2017-06-29 12:54:51)
> On 29 June 2017 at 07:36, Zhenyu Wang wrote:
> > We need to fallback to default supported page size when vGPU is active
> > (intel_vgpu_active() is true).
> > Currently gvt gtt handling can't support huge page entry yet, we
On 29 June 2017 at 07:36, Zhenyu Wang wrote:
> On 2017.06.27 15:54:29 +0100, Matthew Auld wrote:
>> In preparation for supporting huge gtt pages for the ppgtt, we introduce
>> page size members for gem objects. We fill in the page sizes by
>> scanning the sg table.
>>
>>
On 2017.06.27 15:54:29 +0100, Matthew Auld wrote:
> In preparation for supporting huge gtt pages for the ppgtt, we introduce
> page size members for gem objects. We fill in the page sizes by
> scanning the sg table.
>
> v2: pass the sg_mask to set_pages
>
> v3: calculate the sg_mask inline with
In preparation for supporting huge gtt pages for the ppgtt, we introduce
page size members for gem objects. We fill in the page sizes by
scanning the sg table.
v2: pass the sg_mask to set_pages
v3: calculate the sg_mask inline with populating the sg_table where
possible, and pass to set_pages