On 24.04.2024 05:34, Henry Wang wrote: > Hi all, > > This is the remaining series for the full functional "dynamic node > programming using overlay dtbo" feature. The first part [1] has > already been merged. > > Quoting from the original series, the first part has already made > Xen aware of new device tree node which means updating the dt_host > with overlay node information, and in this series, the goal is to > map IRQ and IOMMU during runtime, where we will do the actual IOMMU > and IRQ mapping to a running domain and will call unmap_mmio_regions() > to remove the mapping. > > Also, documentation of the "dynamic node programming using overlay dtbo" > feature is added. > > Patch 1 is a fix of [1] which is noticed during my local test, details > please see the commit message. > > Gitlab CI for this series can be found in [2]. > > [1] > https://lore.kernel.org/xen-devel/20230906011631.30310-1-vikram.garh...@amd.com/ > [2] https://gitlab.com/xen-project/people/henryw/xen/-/pipelines/1265297506 > > Henry Wang (1): > xen/commom/dt-overlay: Fix missing lock when remove the device > > Vikram Garhwal (14): > xen/arm/gic: Enable interrupt assignment to running VM > xen/arm: Always enable IOMMU > tools/libs/light: Always enable IOMMU > tools/libs/light: Increase nr_spi to 160 > rangeset: Move struct range and struct rangeset to headerfile > xen/overlay: Enable device tree overlay assignment to running domains > tools: Add domain_id and expert mode for overlay operations > tools/libs/light: Modify dtbo to domU linux dtbo format > tools/xl: Share overlay with domU > tools/helpers: Add get_overlay > get_overlay: remove domU overlay > xl/overlay: add remove operation to xenstore > add a domU script to fetch overlays and applying them to linux > docs: add device tree overlay documentation
For all the replies I sent, Vikram's addresses - Xilinx or AMD - bounced. What's the value of Cc-ing dead addresses? Jan
