Lines Matching defs:mapping
523 * GEM memory mapping works by handing back to userspace a fake mmap offset
525 * up the object based on the offset and sets up the various memory mapping
549 * GEM memory mapping works by handing back to userspace a fake mmap offset
551 * up the object based on the offset and sets up the various memory mapping
590 * This uses the GFP-mask set on the shmem-mapping (see mapping_set_gfp_mask()).
637 struct address_space *mapping;
643 mapping = obj->filp->f_mapping;
657 mapping_set_unevictable(mapping);
660 p = shmem_read_mapping_page(mapping, i);
670 BUG_ON(mapping_gfp_constraint(mapping, __GFP_DMA32) &&
677 mapping_clear_unevictable(mapping);
722 struct address_space *mapping;
725 mapping = file_inode(obj->filp)->i_mapping;
726 mapping_clear_unevictable(mapping);
1200 * Set up the VMA to prepare mapping of the GEM object using the gem_vm_ops
1212 * drm_gem_mmap() prevents unprivileged users from mapping random objects. So
1228 /* Take a ref for this mapping of the object, so that the fault
1269 * If a driver supports GEM object mapping, mmap calls on the DRM file
Indexes created Mon Sep 29 21:09:56 GMT 2025