Lines Matching defs:mapping
459 * GEM memory mapping works by handing back to userspace a fake mmap offset
461 * up the object based on the offset and sets up the various memory mapping
485 * GEM memory mapping works by handing back to userspace a fake mmap offset
487 * up the object based on the offset and sets up the various memory mapping
524 * This uses the GFP-mask set on the shmem-mapping (see mapping_set_gfp_mask()).
539 struct address_space *mapping;
549 mapping = obj->filp->f_mapping;
563 mapping_set_unevictable(mapping);
568 folio = shmem_read_folio_gfp(mapping, i,
569 mapping_gfp_mask(mapping));
581 BUG_ON(mapping_gfp_constraint(mapping, __GFP_DMA32) &&
588 mapping_clear_unevictable(mapping);
616 struct address_space *mapping;
619 mapping = file_inode(obj->filp)->i_mapping;
620 mapping_clear_unevictable(mapping);
1022 * Set up the VMA to prepare mapping of the GEM object using the GEM object's
1034 * drm_gem_mmap() prevents unprivileged users from mapping random objects. So
1049 /* Take a ref for this mapping of the object, so that the fault
1089 * If a driver supports GEM object mapping, mmap calls on the DRM file
1207 /* Always set the mapping to NULL. Callers may rely on this. */