On 10/29/19 2:51 PM, Chris Wilson wrote:
Quoting Daniele Ceraolo Spurio (2019-10-29 21:46:46)
On 10/29/19 2:58 AM, Matthew Auld wrote:
Since we have no way access it from the CPU. For such cases just
fallback to internal objects.
Since the problem is not limited to rings but it applies to all stolen
objects, wouldn't it be better to just skip the stolen initialization or
return an error from i915_gem_object_create_stolen()?
Not all stolen objects are accessed on the CPU, the problem expressed
here is not universal.
-Chris
ok, please ignore my comment then.
Daniele
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
