Lines Matching full:architecture

117  * And allows the architecture to provide and implement tlb_flush():
135  * If an architecture does not provide tlb_flush() a default implementation
146  *  This might be useful if your architecture has size specific TLB
154  *  Useful if your architecture has non-page page directories.
156  *  When used, an architecture is expected to provide __tlb_remove_table() or
165  *  Useful if your architecture doesn't use IPIs for remote TLB invalidates
170  *  Indicates the architecture has flush_cache_range() but it needs *NOT* be called
179  *  Indicates the architecture wants to merge ranges over VMAs; typical when
184  *  Use this if your architecture lacks an efficient flush_tlb_range(). This
194  *  This is useful if your architecture already flushes TLB entries in the
226  * Without MMU_GATHER_TABLE_FREE the architecture is assumed to have page based
240  * This allows an architecture that does not use the linux page-tables for
413  * When an architecture does not have efficient means of range flushing TLBs
430  * When an architecture does not provide its own tlb_flush() implementation
709  * So if we ever find an architecture
711  * architecture to do its own odd thing, not cause pain for others