Lines Matching full:architecture
111 * And allows the architecture to provide and implement tlb_flush():
129 * If an architecture does not provide tlb_flush() a default implementation
140 * This might be useful if your architecture has size specific TLB
148 * Useful if your architecture has non-page page directories.
150 * When used, an architecture is expected to provide __tlb_remove_table()
158 * Useful if your architecture doesn't use IPIs for remote TLB invalidates
163 * Indicates the architecture has flush_cache_range() but it needs *NOT* be called
172 * Indicates the architecture wants to merge ranges over VMAs; typical when
177 * Use this if your architecture lacks an efficient flush_tlb_range(). This
187 * This is useful if your architecture already flushes TLB entries in the
209 * Without MMU_GATHER_TABLE_FREE the architecture is assumed to have page based
218 * This allows an architecture that does not use the linux page-tables for
362 * When an architecture does not have efficient means of range flushing TLBs
379 * When an architecture does not provide its own tlb_flush() implementation
625 * So if we ever find an architecture
627 * architecture to do its own odd thing, not cause pain for others