mirror of
https://github.com/xen-project/xen.git
synced 2026-10-28 02:01:24 +01:00
Oleksii Kurochko
7e020a4dd6
The device tree Xen builds for dom0/hwdom or for a dom0less domain is only ever consumed by the guest, so a mistake in it surfaces as an obscure failure inside the domain, far away from the code which produced the tree. Add device_tree_dump(). The output follows dtc's format so that a dump can be diffed against the source DTS or fed back to dtc; the value formatting heuristics are ported from dtc's utilfdt_print_data() for that reason. The walk itself goes through libfdt rather than decoding the tag stream by hand as dtc's fdtdump does. Dumping a whole tree is only useful while debugging and costs both code size and a lot of console output, so it is put under its own option, CONFIG_DEVICE_TREE_DUMP. It is separate from CONFIG_DEVICE_TREE_DEBUG because the generated tree is often all that is needed, without the rest of the device tree debug messages. Signed-off-by: Oleksii Kurochko <oleksii.kurochko@gmail.com> Reviewed-by: Michal Orzel <michal.orzel@amd.com>
15 lines
723 B
Makefile
15 lines
723 B
Makefile
obj-y += bootfdt.init.o
|
|
obj-$(CONFIG_HAS_DEVICE_TREE_DISCOVERY) += bootinfo-fdt.init.o
|
|
obj-$(CONFIG_HAS_DEVICE_TREE_DISCOVERY) += bootinfo.init.o
|
|
obj-y += device-tree.o
|
|
obj-$(CONFIG_DOMAIN_BUILD_HELPERS) += domain-build.init.o
|
|
obj-$(filter $(CONFIG_DOM0LESS_BOOT),$(CONFIG_HAS_DEVICE_TREE_DISCOVERY)) += dom0less-build.init.o
|
|
obj-$(CONFIG_DOM0LESS_BOOT) += dom0less-bindings.init.o
|
|
obj-$(CONFIG_OVERLAY_DTB) += dt-overlay.o
|
|
obj-$(CONFIG_DEVICE_TREE_DUMP) += fdt-dump.init.o
|
|
obj-$(CONFIG_HAS_DEVICE_TREE_DISCOVERY) += intc.o
|
|
obj-$(CONFIG_DOMAIN_BUILD_HELPERS) += kernel.o
|
|
obj-$(CONFIG_STATIC_EVTCHN) += static-evtchn.init.o
|
|
obj-$(CONFIG_STATIC_MEMORY) += static-memory.init.o
|
|
obj-$(CONFIG_STATIC_SHM) += static-shmem.init.o
|