<tt>JiangBiao162664/user/zte_ltd Wrote 2016/08/31 10:27:34: > JiangBiao162664/user/zte_ltd</tt> <tt>> 2016/08/31 10:27</tt> <tt>> > From</tt> <tt>> Patrik Jakobsson <patrik.r.jakobsson@gmail.com>, </tt> <tt>> Re: [PATCH] drm/gma500: remove the process of stolen page in page > fault handler.</tt> <tt>> > Patrik Jakobsson <patrik.r.jakobsson@gmail.com> wrote on 2016/08/30 18:21:08: > > > Patrik Jakobsson <patrik.r.jakobsson@gmail.com> </tt> <tt>> > 2016/08/30 18:21</tt> <tt>> > > > From</tt> <tt>> > jiang.biao2@zte.com.cn, > > cc > > dri-devel <dri-devel@lists.freedesktop.org></tt> <tt>> > Re: [PATCH] drm/gma500: remove the process of stolen page in page > fault handler.</tt> <tt>> > > > On Tue, Aug 30, 2016 at 7:10 AM, <jiang.biao2@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 > ></tt> <tt>> As far as I can see, the stolen memory is only used by fbdev driver > in gma500, </tt> <tt>> but the fbdev driver maps the stloen memory directly in psbfb_vm_fault, not </tt> <tt>> using psb_gem_fault to map the stolen memory. </tt> <tt>> The only scenario using the psb_gem_fault is the gtt range created by </tt> <tt>> psb_gem_create, which alloc the gtt range without stolen memory backed. </tt> <tt>> If I missed something, pls enlighten me.</tt> <tt>> Thanks a lot. </tt> <tt>Hi Patrik,</tt> <tt>Could you please help to confirm my question?</tt> <tt>Thank you very much.</tt>