Lines Matching refs:tables

46    the bounds tables between the time when it populates "bndcfgu" and
67    tables. If an entire table becomes unused, we will attempt to free
89  * Frees unused bounds tables at the time that the memory they described
102   * new bounds tables (BT) need to be allocated to save bounds.
107 On-demand kernel allocation of bounds tables
114 tables".
118 hardware during both bounds violations or when the tables are not
119 present. The kernel handles those #BR exceptions for not-present tables
123 The tables need to be accessed and controlled by userspace because
127 tables would obviously destroy performance.
134 :Q: Can virtual space simply be reserved for the bounds tables so that we
136 :A: MPX-enabled application will possibly create a lot of bounds tables in
137     process address space to save bounds information. These tables can take
140     tables can be 4x the size of the data structure being tracked. IOW, a
152     bounds tables?
160 :Q: Could a bounds fault be handed to userspace and the tables allocated
167 bounds tables that we could think of, we create them on demand in
198 Cleanup unused bounds tables
206 Since the kernel allocated those tables on-demand without userspace
211 whether one process is MPX enabled. If yes, those bounds tables covered
217 Two new prctl commands are added to enable and disable MPX bounds tables
238 of bounds tables, it may not create or modify entries in the bounds directory.
240 Certainly users can allocate bounds tables and forcibly point the bounds
243 to assist in managing these tables.