| Message ID | 20250417124844.11143-1-agarciav@amd.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | Hyperlaunch device tree for dom0 | expand |
On Thu Apr 17, 2025 at 1:48 PM BST, Alejandro Vallejo wrote: > Hi, > > Here's a new version. Took a while to integrate all the feedback, but > here it is. > > v4 pipeline: https://gitlab.com/xen-project/people/agvallejo/xen/-/pipelines/1772300721 > > v3: https://lore.kernel.org/xen-devel/20250408160802.49870-1-agarciav@amd.com/ > v2: https://lore.kernel.org/xen-devel/20241226165740.29812-1-dpsmith@apertussolutions.com/ > v1: https://lore.kernel.org/xen-devel/20241123182044.30687-1-dpsmith@apertussolutions.com/ > > Cheers, > Alejandro > > ========= Original cover letter: > > The Hyperlaunch device tree for dom0 series is the second split out for the > introduction of the Hyperlaunch domain builder logic. These changes focus on > introducing the ability to express a domain configuration that is then used to > populate the struct boot_domain structure for dom0. This ability to express a > domain configuration provides the next step towards a general domain builder. > > The splitting of Hyperlaunch into a set of series are twofold, to reduce the > effort in reviewing a much larger series, and to reduce the effort in handling > the knock-on effects to the construction logic from requested review changes. > > Alejandro Vallejo (1): > x86/hyperlaunch: Add helpers to locate multiboot modules > > Daniel P. Smith (12): > x86/boot: add cmdline to struct boot_domain > kconfig: introduce domain builder config options > common/hyperlaunch: introduce the domain builder > x86/hyperlaunch: initial support for hyperlaunch device tree > x86/hyperlaunch: locate dom0 kernel with hyperlaunch > x86/hyperlaunch: obtain cmdline from device tree > x86/hyperlaunch: locate dom0 initrd with hyperlaunch > x86/hyperlaunch: add domain id parsing to domain config > x86/hyperlaunch: specify dom0 mode with device tree > x86/hyperlaunch: add memory parsing to domain config > x86/hyperlaunch: add max vcpu parsing of hyperlaunch device tree > x86/hyperlaunch: add capabilities to boot domain > > xen/arch/x86/Kconfig | 1 + > xen/arch/x86/dom0_build.c | 11 + > xen/arch/x86/hvm/dom0_build.c | 31 +- > xen/arch/x86/include/asm/boot-domain.h | 17 + > xen/arch/x86/include/asm/bootinfo.h | 10 +- > xen/arch/x86/pv/dom0_build.c | 4 +- > xen/arch/x86/setup.c | 91 +++-- > xen/common/Kconfig | 5 + > xen/common/Makefile | 1 + > xen/common/domain-builder/Kconfig | 18 + > xen/common/domain-builder/Makefile | 2 + > xen/common/domain-builder/core.c | 110 ++++++ > xen/common/domain-builder/fdt.c | 488 +++++++++++++++++++++++++ > xen/common/domain-builder/fdt.h | 39 ++ > xen/include/xen/domain-builder.h | 13 + > xen/include/xen/libfdt/libfdt-xen.h | 44 +++ > 16 files changed, 839 insertions(+), 46 deletions(-) > create mode 100644 xen/common/domain-builder/Kconfig > create mode 100644 xen/common/domain-builder/Makefile > create mode 100644 xen/common/domain-builder/core.c > create mode 100644 xen/common/domain-builder/fdt.c > create mode 100644 xen/common/domain-builder/fdt.h > create mode 100644 xen/include/xen/domain-builder.h Bah, I just noticed after sending. The commit messages of the last 10 patches are meant to be common/hyperlaunch. Or just hyperlaunch. It _is_ effectively still x86-only, but it's living under common. Cheers, Alejandro