On Thu, Apr 23, 2015 at 11:14:12AM +0100, Ceraolo Spurio, Daniele wrote:
> On 4/23/2015 10:43 AM, Chris Wilson wrote:
> >On Thu, Apr 23, 2015 at 10:30:01AM +0100, daniele.ceraolospu...@intel.com
> >wrote:
> >>From: Daniele Ceraolo Spurio
> >>
> >>From: Tvrtko Ursulin
> >>
> >>Using imported obje
On 4/23/2015 10:43 AM, Chris Wilson wrote:
On Thu, Apr 23, 2015 at 10:30:01AM +0100, daniele.ceraolospu...@intel.com wrote:
From: Daniele Ceraolo Spurio
From: Tvrtko Ursulin
Using imported objects should not leak i915 vmas (and vms).
In practice this simulates Xorg importing fbcon and leaki
On Thu, Apr 23, 2015 at 10:30:01AM +0100, daniele.ceraolospu...@intel.com wrote:
> From: Daniele Ceraolo Spurio
>
> From: Tvrtko Ursulin
>
> Using imported objects should not leak i915 vmas (and vms).
>
> In practice this simulates Xorg importing fbcon and leaking (or not) one vma
> per Xorg s
From: Daniele Ceraolo Spurio
From: Tvrtko Ursulin
Using imported objects should not leak i915 vmas (and vms).
In practice this simulates Xorg importing fbcon and leaking (or not) one vma
per Xorg startup cycle.
v2: use low-level ioctl wrappers and bo offset to check the leak (Chris)
Signed-o