* Hollis Blanchard <[EMAIL PROTECTED]> [2007-02-23 10:58]: > On Fri, 2007-02-23 at 10:21 -0600, Ryan Harper wrote: > > > > The other method I was going to look into was to allocate dom0's rma, > > and then calculation would look like: > > > > dom0_start_mfn = page_to_mfn(d->arch.rma_base); > > dom0_overlap = (dom0_start_mfn + dom0_nrpages - rma_sz) - > > IO_SIZE_PAGES; > > > > Any other good way to figure how much of dom0's allocation will fall > > within 2-4G IO hole? > > Why are you looking for another approach? What's wrong with this > solution?
I was hoping I'd find this: xen/arch/powerpc/memory.c:145 xenheap_phys_end = xh_pages << PAGE_SHIFT; printk("End of Xen Area: %luMiB (%luKiB)\n", xenheap_phys_end >> 20, xenheap_phys_end >> 10); which marks the end of the xen area; just what I was looking for. Now I can do: /* overlap in pages into 2G-4G IO range (if any) */ dom0_overlap = ((xenheap_phys_end >> PAGE_SHIFT) + dom0_nrpages) - IO_SIZE_PAGES; -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx (512) 838-9253 T/L: 678-9253 [EMAIL PROTECTED] _______________________________________________ Xen-ppc-devel mailing list Xenfirstname.lastname@example.org http://lists.xensource.com/xen-ppc-devel