Lines Matching refs:directory

36 2) That setup code allocates (virtual) space for the "bounds directory",
37    points the "bndcfgu" register to the directory (must also set the valid
47    succeed, and notes the location of the bounds directory. Userspace is
48    expected to keep the bounds directory at that locationWe note it
50    to access the bounds directory register is an expensive operation.
52    issues a bndstx instruction. Since the bounds directory is empty at
55    in the bounds directory point to the new table.
62    the table and remove the entry in the directory.
71  * allocates virtual space for the bounds directory (malloc() essentially)
72  * points the hardware BNDCFGU register at the directory
81    updates the bounds directory to point to the new table. It keeps
114 pointing the bounds-directory over to it.
135    area needs 4*X GB of virtual space, plus 2GB for the bounds directory.
139    ahead of time. Also, a single process's pre-popualated bounds directory
194 When a BNDSTX instruction attempts to save bounds to a bounds directory
217 directory. So kernel have to use XSAVE instruction to get the base
218 of bounds directory from BNDCFG register.
221 optimization, we have to get the base of bounds directory and save it
230 of bounds tables, it may not create or modify entries in the bounds directory.
233 directory at them through XSAVE instruction, and then set valid bit
237 2) Userspace may not take multiple bounds directory entries and point