Lines Matching refs:only

12 Currently it only works for anonymous memory mappings but in the
22 only matters the first time the memory is accessed for the lifetime of
31 TLB can be mapped of larger size only if both KVM and the Linux guest
32 are using hugepages but a significant speedup already happens if only
54   whenever possible (the only possible reservation here is kernelcore=
60 - this initial support only offers the feature in the anonymous memory
82 large region but only touch 1 byte of it, in that case a 2M page might
84 possible to disable hugepages system-wide and to only have them inside
87 Embedded systems should enable hugepages only inside madvise regions
89 only run faster.
98 debugging purposes) or only enabled inside MADV_HUGEPAGE regions (to
182 The transparent_hugepage/enabled values only affect future
221 	every map of the huge zero page, only its allocation.
261 hugetlbfs). Most gup users will only care about the actual physical
284 hugepages being returned (as it's not only checking the pfn of the
367 not only in the head pages, if we want to be able to run
382 page (and only on a tail page) it will find its respective head page,