Hi Alex.
I understand what's going on.
(I wrote the last mail in hurry. so I didn't look the log so closely.
sorry for that)
> (XEN) mem40: type=11, attr=0x1, range=[0x0000080000000000-0x0000100000000000)
> (8388608MB)
Plase note that type = 11 = EFI_MEMORY_MAPPED_IO
About 8TB (~= 8388608MB / 1024) is required to map this range
to dom0 for the P2M conversion table.
This is the reason why the xenheap is used up.
Allocating from domheap instead of xenheap doesn't solve because
8TB is too huge.
I didn't expect such a huge range.
(BTW What is the MMIO range is used for?)
Perhaps you may see dom0 boot message by skipping to map the MMIO range.
If dom0 tries to do access the MMIO range, something go wrong though.
dom_fw_init()
=>efi_memmap_walk_type(EFI_MEMORY_MAPPED_IO,
dom_fw_dom0_passthrough, &arg);
=> dom_fw_dom0_passthrough() <<<<<<<<< modify this function.
Maybe some special code for handling such a huge range is needed.
thanks.
On Sat, Apr 08, 2006 at 11:20:30AM -0600, Alex Williamson wrote:
> On Sat, 2006-04-08 at 13:41 +0900, Isaku Yamahata wrote:
>
> > Could you try again with the following work around patch?
> > This patch may break something, but this patch may help
> > to track down this issue.
> >
>
> Hi Yamata,
>
> I tried alloc_domheap_pages(NULL, 0, 0) in pgtable_quicklist_alloc().
> I don't have physical access to the system right now to remove ram,
> instead I booted with max_addr=1G on the xen half of the append line.
> With that I hit a BUG in ia64_handle_reflection(). Here's the log.
> Thanks,
>
> Alex
--
yamahata
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home