Message ID | alpine.DEB.2.21.2004141746350.8746@sstabellini-ThinkPad-T480s (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On 15/04/2020 02:02, Stefano Stabellini wrote: > Hi all, > > This series adds support for 1:1 mapping (guest physical == physical) > the memory of dom0less domUs. The memory ranges assigned to a domU can be > explicitly chosen by the user at boot time. > > This is desirable in cases where an IOMMU is not present in the system, > or it cannot be used. For instance, it might not be usable because it > doesn't cover a specific device, or because it doesn't have enough > bandwidth, or because it adds too much latency. In these cases, the user > should use a MPU to protect the memory in the system (e.g. the Xilinx > XMPU), configuring it with the chosen address ranges. > > Cheers, > > Stefano > > > > The following changes since commit 7372466b21c3b6c96bb7a52754e432bac883a1e3: > > x86/mem_sharing: Fix build with !CONFIG_XSM (2020-04-10 15:20:10 +0100) > > are available in the Git repository at: > > http://xenbits.xenproject.org/git-http/people/sstabellini/xen-unstable.git direct-map-1 > > for you to fetch changes up to 43503720ab6851a28a66fdd067f592d5354ae83a: > > xen/arm: call iomem_permit_access for passthrough devices (2020-04-14 17:42:21 -0700) > > ---------------------------------------------------------------- > Stefano Stabellini (12): > xen: introduce xen_dom_flags > xen/arm: introduce arch_xen_dom_flags and direct_map > xen/arm: introduce 1:1 mapping for domUs > xen: split alloc_heap_pages in two halves for reusability > xen: introduce reserve_heap_pages > xen/arm: reserve 1:1 memory for direct_map domUs > xen/arm: new vgic: rename vgic_cpu/dist_base to c/dbase > xen/arm: if is_domain_direct_mapped use native addresses for GICv2 > xen/arm: if is_domain_direct_mapped use native addresses for GICv3 > xen/arm: if is_domain_direct_mapped use native UART address for vPL011 The 3 patches above cover addresses but not interrupts. Why? Cheers,
On Thu, 16 Apr 2020, Julien Grall wrote: > > Stefano Stabellini (12): > > xen: introduce xen_dom_flags > > xen/arm: introduce arch_xen_dom_flags and direct_map > > xen/arm: introduce 1:1 mapping for domUs > > xen: split alloc_heap_pages in two halves for reusability > > xen: introduce reserve_heap_pages > > xen/arm: reserve 1:1 memory for direct_map domUs > > xen/arm: new vgic: rename vgic_cpu/dist_base to c/dbase > > xen/arm: if is_domain_direct_mapped use native addresses for GICv2 > > xen/arm: if is_domain_direct_mapped use native addresses for GICv3 > > xen/arm: if is_domain_direct_mapped use native UART address for vPL011 > > The 3 patches above cover addresses but not interrupts. Why? Hi Julien, I take that you are referring to GUEST_VPL011_SPI, right?
Hi Stefano, On 29/04/2020 21:16, Stefano Stabellini wrote: > On Thu, 16 Apr 2020, Julien Grall wrote: >>> Stefano Stabellini (12): >>> xen: introduce xen_dom_flags >>> xen/arm: introduce arch_xen_dom_flags and direct_map >>> xen/arm: introduce 1:1 mapping for domUs >>> xen: split alloc_heap_pages in two halves for reusability >>> xen: introduce reserve_heap_pages >>> xen/arm: reserve 1:1 memory for direct_map domUs >>> xen/arm: new vgic: rename vgic_cpu/dist_base to c/dbase >>> xen/arm: if is_domain_direct_mapped use native addresses for GICv2 >>> xen/arm: if is_domain_direct_mapped use native addresses for GICv3 >>> xen/arm: if is_domain_direct_mapped use native UART address for vPL011 >> >> The 3 patches above cover addresses but not interrupts. Why? > > Hi Julien, > > I take that you are referring to GUEST_VPL011_SPI, right? GUEST_VPL011_SPI is at least one of them. For long term, we may want to consider PPIs as well (e.g timer). Cheers,