Lines Matching refs:directory

42 2) That setup code allocates (virtual) space for the "bounds directory",
43    points the "bndcfgu" register to the directory (must also set the valid
53    succeed, and notes the location of the bounds directory. Userspace is
54    expected to keep the bounds directory at that location. We note it
56    to access the bounds directory register is an expensive operation.
58    issues a bndstx instruction. Since the bounds directory is empty at
61    in the bounds directory point to the new table.
68    the table and remove the entry in the directory.
77  * allocates virtual space for the bounds directory (malloc() essentially)
78  * points the hardware BNDCFGU register at the directory
87    updates the bounds directory to point to the new table. It keeps
121 pointing the bounds-directory over to it.
142     area needs 4*X GB of virtual space, plus 2GB for the bounds directory.
146     ahead of time. Also, a single process's pre-populated bounds directory
201 When a BNDSTX instruction attempts to save bounds to a bounds directory
225 directory. So kernel have to use XSAVE instruction to get the base
226 of bounds directory from BNDCFG register.
229 optimization, we have to get the base of bounds directory and save it
238 of bounds tables, it may not create or modify entries in the bounds directory.
241 directory at them through XSAVE instruction, and then set valid bit
245 2) Userspace may not take multiple bounds directory entries and point