Searched hist:209048 (Results 1 - 9 of 9) sorted by relevance
| /freebsd-10.1-release/sys/powerpc/booke/ | ||
| H A D | pmap.c | diff 209048 Fri Jun 11 13:54:43 MDT 2010 alc Relax one of the new assertions in pmap_enter() a little. Specifically, allow pmap_enter() to be performed on an unmanaged page that doesn't have VPO_BUSY set. Having VPO_BUSY set really only matters for managed pages. (See, for example, pmap_remove_write().) |
| /freebsd-10.1-release/sys/i386/xen/ | ||
| H A D | pmap.c | diff 209048 Fri Jun 11 13:54:43 MDT 2010 alc Relax one of the new assertions in pmap_enter() a little. Specifically, allow pmap_enter() to be performed on an unmanaged page that doesn't have VPO_BUSY set. Having VPO_BUSY set really only matters for managed pages. (See, for example, pmap_remove_write().) |
| /freebsd-10.1-release/sys/powerpc/aim/ | ||
| H A D | mmu_oea64.c | diff 209048 Fri Jun 11 13:54:43 MDT 2010 alc Relax one of the new assertions in pmap_enter() a little. Specifically, allow pmap_enter() to be performed on an unmanaged page that doesn't have VPO_BUSY set. Having VPO_BUSY set really only matters for managed pages. (See, for example, pmap_remove_write().) |
| H A D | mmu_oea.c | diff 209048 Fri Jun 11 13:54:43 MDT 2010 alc Relax one of the new assertions in pmap_enter() a little. Specifically, allow pmap_enter() to be performed on an unmanaged page that doesn't have VPO_BUSY set. Having VPO_BUSY set really only matters for managed pages. (See, for example, pmap_remove_write().) |
| /freebsd-10.1-release/sys/arm/arm/ | ||
| H A D | pmap.c | diff 209048 Fri Jun 11 13:54:43 MDT 2010 alc Relax one of the new assertions in pmap_enter() a little. Specifically, allow pmap_enter() to be performed on an unmanaged page that doesn't have VPO_BUSY set. Having VPO_BUSY set really only matters for managed pages. (See, for example, pmap_remove_write().) |
| /freebsd-10.1-release/sys/ia64/ia64/ | ||
| H A D | pmap.c | diff 209048 Fri Jun 11 13:54:43 MDT 2010 alc Relax one of the new assertions in pmap_enter() a little. Specifically, allow pmap_enter() to be performed on an unmanaged page that doesn't have VPO_BUSY set. Having VPO_BUSY set really only matters for managed pages. (See, for example, pmap_remove_write().) |
| /freebsd-10.1-release/sys/mips/mips/ | ||
| H A D | pmap.c | diff 209048 Fri Jun 11 13:54:43 MDT 2010 alc Relax one of the new assertions in pmap_enter() a little. Specifically, allow pmap_enter() to be performed on an unmanaged page that doesn't have VPO_BUSY set. Having VPO_BUSY set really only matters for managed pages. (See, for example, pmap_remove_write().) |
| /freebsd-10.1-release/sys/sparc64/sparc64/ | ||
| H A D | pmap.c | diff 209048 Fri Jun 11 13:54:43 MDT 2010 alc Relax one of the new assertions in pmap_enter() a little. Specifically, allow pmap_enter() to be performed on an unmanaged page that doesn't have VPO_BUSY set. Having VPO_BUSY set really only matters for managed pages. (See, for example, pmap_remove_write().) |
| /freebsd-10.1-release/sys/i386/i386/ | ||
| H A D | pmap.c | diff 209048 Fri Jun 11 13:54:43 MDT 2010 alc Relax one of the new assertions in pmap_enter() a little. Specifically, allow pmap_enter() to be performed on an unmanaged page that doesn't have VPO_BUSY set. Having VPO_BUSY set really only matters for managed pages. (See, for example, pmap_remove_write().) |
Completed in 618 milliseconds