On 4/23/2015 12:36 PM, Chris Wilson wrote:
On Thu, Apr 23, 2015 at 12:23:17PM +0100, daniele.ceraolospu...@intel.com wrote:
From: Tvrtko Ursulin tvrtko.ursu...@intel.com
Using imported objects should not leak i915 vmas (and vms).
In practice this simulates Xorg importing fbcon and leaking (or
On Thu, Apr 23, 2015 at 02:01:43PM +0100, Ceraolo Spurio, Daniele wrote:
On 4/23/2015 12:36 PM, Chris Wilson wrote:
+ memset(execbuf, 0, sizeof(execbuf));
+ execbuf.buffers_ptr = (uintptr_t)exec;
+ execbuf.buffer_count = 1;
+ execbuf.batch_len = sizeof(batch_data);
+ execbuf.flags
On 04/23/2015 12:23 PM, daniele.ceraolospu...@intel.com wrote:
From: Tvrtko Ursulin tvrtko.ursu...@intel.com
I have least to do with the current version so best upgrade yourself as
author now!
Regards,
Tvrtko
___
Intel-gfx mailing list
From: Tvrtko Ursulin tvrtko.ursu...@intel.com
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)
v3: use the
On Thu, Apr 23, 2015 at 12:23:17PM +0100, daniele.ceraolospu...@intel.com wrote:
From: Tvrtko Ursulin tvrtko.ursu...@intel.com
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.