Hi Leif, I have make a new multiboot support patch V3.4 following Ian's suggestion for V3.1
But I met some problem on the latest xen for multiboot development branch, so I am still using the staging branch of xen repo.
To Ian: Could we just work together to figure them out next week? Can Xen support two blanks of RAM for now? it seems the new linaro-edk2 (2014.06) will allocate memory from the high end of ram, that cause the failure.
Some pending change: (1)delete "grub_arm64_disable_caches_mmu" and the relevant code(misc.c and misc_irq.S)(waiting for stub-xen) (2)non-stub xen boot switch to stub-xen boot (waiting for stub-xen) (3)align info (need more info from Ian, or do we need --align ?) (4)the compatibility strings: "xen,*" ---> "multiboot,*" (need Ian's multiboot branch) (5)grub coding style (will do in next patch) (6)integrate multiboot_fdt.c back to multiboot.c (will make a new patch/branch for it, but I think multiboot_fdt.c make multiboot.c more generic)
Now this patch works fine with the staging branch of xen. Will update the wiki patch, in case someone want to try it. :-)
Notice: This patch bases on master branch of upstream grub
On Fri, 2014-06-20 at 13:26 +0800, Fu Wei wrote:
Hi Leif, I have make a new multiboot support patch V3.4 following Ian's suggestion for V3.1
But I met some problem on the latest xen for multiboot development branch, so I am still using the staging branch of xen repo.
To Ian: Could we just work together to figure them out next week?
I'm hoping to get back to those patches either later this week or early next week.
Can Xen support two blanks of RAM for now?
(I assume you mean "banks"). It should do. At the moment it doesn't support very sparse physical address spaces (i.e. two banks with a big gap between them) but it should handle that gracefully by ignoring one bank. I've got a pending TODO item to sort that out of course since we don't want to be wasting RAM like that.
(3)align info (need more info from Ian, or do we need --align ?)
Lets not bother, it was just an interesting idea for an optional extension which might be useful. We can safely not bother though I think.
Ian.
On 06/24/2014 08:47 PM, Ian Campbell wrote:
On Fri, 2014-06-20 at 13:26 +0800, Fu Wei wrote:
Hi Leif, I have make a new multiboot support patch V3.4 following Ian's suggestion for V3.1
But I met some problem on the latest xen for multiboot development branch, so I am still using the staging branch of xen repo.
To Ian: Could we just work together to figure them out next week?
I'm hoping to get back to those patches either later this week or early next week.
Thanks, let me know, once you fix those problem in your multiboot branch.
Can Xen support two blanks of RAM for now?
(I assume you mean "banks"). It should do. At the moment it doesn't support very sparse physical address spaces (i.e. two banks with a big gap between them) but it should handle that gracefully by ignoring one bank. I've got a pending TODO item to sort that out of course since we don't want to be wasting RAM like that.
So sorry for that typo! Yes, I mean "banks". The old linaro-edk2 allocate memory from "low bank" memory, but the latest one try to allocate memory from high end of the "high bank". For FVP base, there is a big gap between two banks. So maybe that is the problem. Will try to confirm it by some experiment. :-)
But I think we need to add this support to xen ASAP.
(3)align info (need more info from Ian, or do we need --align ?)
Lets not bother, it was just an interesting idea for an optional extension which might be useful. We can safely not bother though I think.
np, just use the default align. :-)
Great thanks for your feedback!
Please let me know if you have other suggestions for my new patch.
Ian.
-
Fu Wei -
Ian Campbell