Lines Matching full:bind

28  * user bind operations.
32  * Bind jobs
35  * A bind job consist of two batches and runs either on the migrate engine
36  * (kernel binds) or the bind engine passed in (user binds). In both cases the
40  * the bind VM page table BOs which need to be updated. A physical page is
41  * required for this. If it is a user bind, the page is allocated from pool of
42  * pages reserved user bind operations with drm_suballoc managing this pool. If
43  * it is a kernel bind, the page reserved for kernel binds is used.
46  * has VRAM the bind VM page table BOs are in VRAM and the identity mapping can
49  * The second batch is used to program page table updated in the bind VM. Why
53  * When the bind job complete, the page allocated is returned the pool of pages
54  * reserved for user bind operations if a user bind. No need do this for kernel