From 44e6cbd7c84212bafefbeafe5c66cc38af64b7b6 Mon Sep 17 00:00:00 2001 From: neel Date: Wed, 3 Jul 2013 23:38:37 +0000 Subject: vm_phys_fictitious_reg_range() was losing the 'memattr' because it would be reset by pmap_page_init() right after being initialized in vm_page_initfake(). The statement above is with reference to the amd64 implementation of pmap_page_init(). Fix this by calling 'pmap_page_init()' in 'vm_page_initfake()' before changing the 'memattr'. Reviewed by: kib MFC after: 2 weeks --- sys/vm/vm_page.c | 1 + 1 file changed, 1 insertion(+) (limited to 'sys/vm/vm_page.c') diff --git a/sys/vm/vm_page.c b/sys/vm/vm_page.c index 65ca2e3..a47209f 100644 --- a/sys/vm/vm_page.c +++ b/sys/vm/vm_page.c @@ -645,6 +645,7 @@ vm_page_initfake(vm_page_t m, vm_paddr_t paddr, vm_memattr_t memattr) /* Fictitious pages don't use "order" or "pool". */ m->oflags = VPO_BUSY | VPO_UNMANAGED; m->wire_count = 1; + pmap_page_init(m); memattr: pmap_page_set_memattr(m, memattr); } -- cgit v1.1