Lines Matching full:architectures

26  * On almost all architectures and configurations, 0 can be used as the
27  * upper ceiling to free_pgtables(): on many architectures it has the same
190  * is issued.  Some architectures may benefit from doing this, and it is
374  * Architectures that automatically set the access bit should overwrite it.
416  * For walking the pagetables without holding any locks.  Some architectures
559  * gives up, simply does nothing, and continues; on architectures where
573  * Some architectures may be able to avoid expensive synchronization
626  * On some architectures hardware does not set page access bit when accessing
735  * Doing so can allow in certain architectures to avoid a TLB flush in most
755  * Some architectures provide facilities to virtualization guests
860  * Some architectures support metadata associated with a page. When a
878  * Some architectures support metadata associated with a page. When a
895  * Allow architectures to preserve additional metadata associated with
1531  * Some architectures don't define certain PAGE_KERNEL_* flags. This is either
1534  * fallbacks, as best effort, which we can count on in lieu of the architectures
1574  * ZSMALLOC needs to know the highest PFN on 32-bit architectures
1592  * On some architectures it depends on the mm if the p4d/pud or pmd
1654  * Some architectures have MMUs that are configurable or selectable at boot