Justin Hibbits d7c0543ff8 powerpc/booke: Add pte_find_next() to find the next in-use PTE ... Summary: Iterating over VM_MIN_ADDRESS->VM_MAXUSER_ADDRESS can take a very long time iterating one page at a time (2**(log_2(SIZE)-12) operations), yielding possibly several days or even weeks on 64-bit Book-E, even for a largely empty, which can happen when swapping out a process by vmdaemon. Speed this up by instead finding the next PTE at or equal to the given VA. Reviewed by: bdragon Differential Revision: https://reviews.freebsd.org/D24238		2020-04-11 00:16:50 +00:00
..
booke_machdep.c	[PowerPC] Fix VSX context handling	2020-02-04 20:40:45 +00:00
locore.S	powerpc/booke: Fix 32-bit Book-E SMP AP bringup	2019-12-04 03:41:55 +00:00
machdep_e500.c	powerpc: Axe PPC4xx support.	2020-03-18 01:09:43 +00:00
mp_cpudep.c
platform_bare.c
pmap_32.c	powerpc/booke: Add pte_find_next() to find the next in-use PTE	2020-04-11 00:16:50 +00:00
pmap_64.c	powerpc/booke: Add pte_find_next() to find the next in-use PTE	2020-04-11 00:16:50 +00:00
pmap.c	powerpc/booke: Add pte_find_next() to find the next in-use PTE	2020-04-11 00:16:50 +00:00
spe.c	powerpc: Simplify _nodrop variants of FPU and vector register saves	2020-03-13 01:27:37 +00:00
trap_subr.S	powerpc/booke: Change Book-E 64-bit pmap to 4-level table	2020-04-11 00:12:34 +00:00