AFAICT the patch can be divided in two:
1) Dom0 SMC forward
While we did some work around trapping SMC, we still don't forward them
directly to the firmware. If you need to forward Dom0 SMC call to the
firmware, then we first need to know what they are used for. I would
prefer a whilelisting over forward everything (even for Dom0).
2) SMP support for Odroid-XU
This part would need to be cleaned up. We need to ensure the SMP
bring-up is still working with the other exynos platform.
Feel free to send patches on xen-devel, I would be happy to review them.
> What I am completely stuck on is getting a modern dom0 working. The
> handful of patches in
> https://github.com/bkrepo/linux-dom0/commits/odroidxu3-3.10.y-xen seem
> only to enable the relevant config options, patch the device tree with
> the arch timer and "xen-dom0" passthrough section, and backport the
> PSCI support which is already in 4.14, so I've tried applying these
> changes to the ODROID 4.14 tree at
> https://github.com/hardkernel/linux, with no success.
> Using the FDT from the working 3.x dom0 with the 4.14 zImage, it boots
> but doesn't seem to find any of the underlying hardware, certainly not
> the USB attached SSD which I need to boot.
I would not recommend to use the 3.x FDT with 4.14. Despite the DT
should be agnostic to the kernel revision, there are still often changes
> Using the FDT from the ODROID 4.14 tree, patched for arch timer and
> the xen-dom0 section, the hypervisor sticks at "(XEN) 3..."
I am not entirely sure to understand why you need to patch the arch
timer. Could you send the diff of the FDT?
I would also recommend to make sure the same configuration boots without
Xen. This will tell you whether the bug is in Xen or Linux.
> Unfortunately I'm not at all familiar with either Xen or the ARM
> architecture, so would really appreciate it if anyone could steer me
> in the right direction!
I hope I provided enough details. Feel free to ask any questions.