Re: UMA allocations from a specific physical range

2010-09-06 Thread Alan Cox
m...@freebsd.org wrote: [snip] IIRC the memory from vm_phys_alloc_contig() can be released like any other page; the interface should just be fetching a specific page. How far off is the page wire count? I'm assuming it's hitting the assert that it's 1? I think vm_page_free() is the right

Re: UMA allocations from a specific physical range

2010-09-05 Thread mdf
On Mon, Sep 6, 2010 at 1:38 AM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: PowerPC hypervisors typically provided a restricted range on memory when the MMU is disabled, as it is when initially handling exceptions. In order to restore virtual memory, the powerpc64 code needs to read a data

Re: UMA allocations from a specific physical range

2010-09-05 Thread Nathan Whitehorn
On 09/05/10 22:51, m...@freebsd.org wrote: On Mon, Sep 6, 2010 at 1:38 AM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: PowerPC hypervisors typically provided a restricted range on memory when the MMU is disabled, as it is when initially handling exceptions. In order to restore virtual

Re: UMA allocations from a specific physical range

2010-09-05 Thread mdf
On Mon, Sep 6, 2010 at 4:28 AM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 09/05/10 22:51, m...@freebsd.org wrote: On Mon, Sep 6, 2010 at 1:38 AM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: PowerPC hypervisors typically provided a restricted range on memory when the MMU is