Lines Matching full:mapping

9 devmap \- validate and translate virtual mapping for memory mapped device
38 An opaque mapping handle that the system uses to describe the mapping.
47 User offset within the logical device memory at which the mapping begins.
56 Length (in bytes) of the mapping to be mapped.
65 Pointer to length (in bytes) of mapping that has been validated. \fImaplen\fR
81 mapping. A memory mapped device has memory  that can be mapped into a process's
88 entry point during the mapping setup when \fBD_DEVMAP\fR is set in the
116 physical offset within the device address space, and to pass the mapping
117 information to the system for setting up the mapping.
120 \fIdhp\fR is a device mapping handle that the system uses to describe a mapping
122 virtual address space. The system may create multiple mapping  handles in one
123 \fBmmap\fR(2) system call (for example, if the mapping contains multiple
141 The system will repeatedly call \fBdevmap()\fR until the original mapping
146 The \fBdevmap()\fR entry point must initialize the mapping parameters before
150 initializes the mapping parameters by mapping the control callback structure
151 (see \fBdevmap_callback_ctl\fR(9S)), the device access attributes, mapping
152 length, maximum protection possible for the mapping, and optional mapping
154 further information on initializing the mapping parameters.
163 For device mappings, the system establishes the mapping to the physical address
168 For kernel memory mapping, the system selects a user virtual address that is
193 point. For mapping device memory, \fBdevmap()\fR calls
195 offset within the register, \fIroff\fR. For mapping kernel memory, the driver
209 #define MAPPING_SIZE 0x2000        /* size of the mapping */
211                                       of the mapping */
263       callbackops = &xxmap_ops;  /* do all callbacks for this mapping */
275       callbackops = NULL;        /* don't do callback for this mapping */