[PATCH] drm/gma500: remove the process of stolen page in page fault handler.
jiang.biao2 at zte.com.cn
jiang.biao2 at zte.com.cn
Wed Aug 31 02:27:34 UTC 2016
Patrik Jakobsson <patrik.r.jakobsson at gmail.com> wrote on 2016/08/30 18:21:08:
> Patrik Jakobsson <patrik.r.jakobsson at gmail.com>
> 2016/08/30 18:21
>
> From
> jiang.biao2 at zte.com.cn,
> cc
> dri-devel <dri-devel at lists.freedesktop.org>
> Re: [PATCH] drm/gma500: remove the process of stolen page in page fault handler.
>
> On Tue, Aug 30, 2016 at 7:10 AM, <jiang.biao2 at zte.com.cn> 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 do need this.
>
> -Patrik
>
As far as I can see, the stolen memory is only used by fbdev driver in gma500,
but the fbdev driver maps the stloen memory directly in psbfb_vm_fault, not
using psb_gem_fault to map the stolen memory.
The only scenario using the psb_gem_fault is the gtt range created by
psb_gem_create, which alloc the gtt range without stolen memory backed.
If I missed something, pls enlighten me.
Thanks a lot.
More information about the dri-devel
mailing list