Warning: file_get_contents(https://raw.githubusercontent.com/Den1xxx/Filemanager/master/languages/ru.json): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in /home/familylifersmpc/htdocs/www.familylifersmpc.com/index.php on line 91
/* SPDX-License-Identifier: GPL-2.0 */ #ifndef _PARISC_TLBFLUSH_H #define _PARISC_TLBFLUSH_H /* TLB flushing routines.... */ #include #include #include extern void flush_tlb_all(void); extern void flush_tlb_all_local(void *); #define smp_flush_tlb_all() flush_tlb_all() int __flush_tlb_range(unsigned long sid, unsigned long start, unsigned long end); #define flush_tlb_range(vma, start, end) \ __flush_tlb_range((vma)->vm_mm->context, start, end) #define flush_tlb_kernel_range(start, end) \ __flush_tlb_range(0, start, end) /* * flush_tlb_mm() * * The code to switch to a new context is NOT valid for processes * which play with the space id's. Thus, we have to preserve the * space and just flush the entire tlb. However, the compilers, * dynamic linker, etc, do not manipulate space id's, so there * could be a significant performance benefit in switching contexts * and not flushing the whole tlb. */ static inline void flush_tlb_mm(struct mm_struct *mm) { BUG_ON(mm == &init_mm); /* Should never happen */ #if 1 || defined(CONFIG_SMP) /* Except for very small threads, flushing the whole TLB is * faster than using __flush_tlb_range. The pdtlb and pitlb * instructions are very slow because of the TLB broadcast. * It might be faster to do local range flushes on all CPUs * on PA 2.0 systems. */ flush_tlb_all(); #else /* FIXME: currently broken, causing space id and protection ids * to go out of sync, resulting in faults on userspace accesses. * This approach needs further investigation since running many * small applications (e