Lines Matching full:update

116 not as easy as CPU page table updates. To update the device page table, you must
118 specific commands in it to perform the update (unmap, cache invalidations, and
173       * @update: update information (see struct mmu_notifier_range)
174       * Return: -EAGAIN if update.blockable false and callback need to
178       * page table is updated. The device driver must update its page table
179       * in response to this callback. The update argument tells what action
187                                        const struct hmm_update *update);
190 The device driver must perform the update action to the range (mark range
191 read only, or fully unmap, etc.). The device must complete the update before
250       take_lock(driver->update);
252           release_lock(driver->update);
257       // Use pfns array content to update device page table
260       release_lock(driver->update);
265 The driver->update lock is the same lock that the driver takes inside its
267 hmm_range_valid() to avoid any race with a concurrent CPU page table update.
275 update their own page table. Device updates are a multi-step process. First,
278 the buffer that the update is done. Creating and scheduling the update command