From: Abdiel Janulgue
CPU mmap implementation depending on the object's backing pages.
At the moment we introduce shmem and local-memory BAR fault handlers
Note that the mmap type is done one at a time to circumvent the DRM
offset manager limitation. Note that we multiplex mmap_gtt and
mmap_offse
Quoting Matthew Auld (2019-02-14 14:57:28)
> @@ -157,6 +163,10 @@ struct drm_i915_gem_object {
> unsigned int userfault_count;
> struct list_head userfault_link;
>
> + enum i915_cpu_mmap_origin_type mmap_origin;
> + atomic_t mmap_count;
> + u64 mmap_flags;
These
On 14/02/2019 14:57, Matthew Auld wrote:
From: Abdiel Janulgue
CPU mmap implementation depending on the object's backing pages.
depends?
At the moment we introduce shmem and local-memory BAR fault handlers
Note that the mmap type is done one at a time to circumvent the DRM
offset manager l
Quoting Tvrtko Ursulin (2019-02-26 13:34:51)
>
> On 14/02/2019 14:57, Matthew Auld wrote:
> > From: Abdiel Janulgue
> >
> > CPU mmap implementation depending on the object's backing pages.
>
> depends?
>
> > At the moment we introduce shmem and local-memory BAR fault handlers
> > Note that the
