Lines Matching refs:this

10 More specifically, some use cases that this library aims to support are:
43 From this point onwards, this document will implicitly refer to version 2 of the
89 potentially less memory.  However, if part of this 2MB region is later remapped
93 modified to point to this new level-3 table. This has a performance cost at
97 then they might enforce a 4KB mapping granularity for this 2MB region from the
102 library will choose the mapping granularity for this region as it sees fit (more
128   The resulting translation context variable will be called after this name, to
138   Number of translation tables to statically allocate for this context,
140   allocated. For example, if the initial lookup level is 1, this parameter would
142   for this context.
146   Size in bytes of the virtual address space to map using this context. This
153   Size in bytes of the physical address space to map using this context.
193 Although this feature provides some level of dynamic memory allocation, this
197 does not fit within this pre-allocated pool of memory.
203 The external APIs exposed by this library are declared and documented in the
205 getting information about the usage of the different APIs this library
220 As explained earlier in this document, when the dynamic mapping feature is
222 static regions. For this reason (and to retain backward compatibility with the
233 off. In practice, the usual call flow would look like this:
242 #. At this point, it is no longer possible to add static regions. Dynamic
323 some point, the library has to convert this information into actual translation
327 mmap regions list. Adding a static or dynamic region at this point through one
370 them. Even though this ordering is only strictly needed for overlapping static
386 A counter-example is the initialization of translation tables. In this case,
396 that was not mapped in this translation regime and the library will have
399 invalid translation table entry [#tlb-no-invalid-entry]_, this means that this