Patrik Jakobsson wrote 2016/09/02 21:54:41:
> Patrik Jakobsson
> 2016/09/02 21:54
>
> Re: [PATCH] drm/gma500: remove the process of stolen page in page
> fault handler.
>
> On Fri, Sep 2, 2016 at 11:31 AM, wrote:
> >
> > JiangBiao162664/user/
JiangBiao162664/user/zte_ltd Wrote 2016/08/31 10:27:34:
> JiangBiao162664/user/zte_ltd
> 2016/08/31 10:27
>
> From
> Patrik Jakobsson ,
> Re: [PATCH] drm/gma500: remove the process of stolen page in page
> fault handler.
>
> Patrik Jakobsson wrote on 2016/08/
On Fri, Sep 2, 2016 at 11:31 AM, wrote:
>
> JiangBiao162664/user/zte_ltd Wrote 2016/08/31 10:27:34:
>
>> JiangBiao162664/user/zte_ltd
>> 2016/08/31 10:27
>>
>> From
>> Patrik Jakobsson ,
>> Re: [PATCH] drm/gma500: remove the process of stolen page in
Patrik Jakobsson wrote on 2016/08/30 18:21:08:
> Patrik Jakobsson
> 2016/08/30 18:21
>
> From
> jiang.biao2 at zte.com.cn,
> cc
> dri-devel
> Re: [PATCH] drm/gma500: remove the process of stolen page in page fault
> handler.
>
> On Tue, Aug 30, 2016 at 7:1
Direct gtt range is used in the page fault scene in current driver,
instead of stolen page. So no need to keep relative process.
---
drivers/gpu/drm/gma500/gem.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/gma500/gem.c b/drivers/gpu/drm/gma500/gem.c
in
On Tue, Aug 30, 2016 at 7:10 AM, wrote:
>
> Direct gtt range is used in the page fault scene in current driver,
> instead of stolen page. So no need to keep relative process.
Hi
Are you saying that we don't use stolen memory? Afaik stolen memory
should be accessed through the stolen range so we
