Hi, Alex
Thank you for your comments.
I agree, my patch can be applied after fixing .config(of discontigous issue),
fixing and optimizing them, and so on.
Also, as Mark said, xen-ia64 may not need to allocate
all memory and cpu to dom0. IA64 machine is very large system,
and dom0 don't need large machine environment.
Best Regards,
Akio Takebe
>On Thu, 2007-01-18 at 13:06 +0900, Akio Takebe wrote:
>> Hi,
>>
>> If we don't specify dom0_mem, we can use all memory on dom0 with this patch.
>> I change alloc_dom0() to alloc_dom0_size(), and alloc_dom0_size() is
>> static function.
>
>Hi Akio,
>
> I don't think we're able to do this yet. One of my test systems is
>an rx6600 w/ 96G of memory. With this patch, I get a _very_ long pause
>during Xen boot (>30 seconds), followed by an endless loop of page
>allocation failures:
>
>(XEN) Domain0 EFI passthrough: ACPI 2.0=0x3fdce000 SMBIOS=0x3e52a000
>[long pause here]
>(XEN) Cannot handle page request order 0!
>(XEN) Cannot handle page request order 0!
>(XEN) Cannot handle page request order 0!
>(XEN) Cannot handle page request order 0!
>(XEN) Cannot handle page request order 0!
>...
>
>The most memory I can specify for dom0_mem and still boot seems to be
>around 87G. Obviously failing to boot is bad, but the long pause while
>we're individually mapping every page for dom0 is also a usability
>issue. We either need to see about optimizing this code segment to
>reduce the delay to something acceptable, or add some kind of forward
>progress indicator. Thanks,
>
> Alex
>
>--
>Alex Williamson HP Open Source & Linux Org.
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home