search for: resv_t_identity

...s to be behind different physical IOMMUs. For reserved regions, we specify what the driver should do and what the device should enforce with regard to mapping IOVAs of overlapping regions. For example, if a device has some virtual address RESV_T_MSI and an other device has the same virtual address RESV_T_IDENTITY, what should the driver do? I think it should apply the RESV_T_IDENTITY. RESV_T_MSI is just a special case of RESV_T_RESERVED, it's a hint for the IRQ subsystem and doesn't have a meaning within a domain. From DMA mappings point of view, it is effectively the same as RESV_T_RESERVED. When...

...s to be behind different physical IOMMUs. For reserved regions, we specify what the driver should do and what the device should enforce with regard to mapping IOVAs of overlapping regions. For example, if a device has some virtual address RESV_T_MSI and an other device has the same virtual address RESV_T_IDENTITY, what should the driver do? I think it should apply the RESV_T_IDENTITY. RESV_T_MSI is just a special case of RESV_T_RESERVED, it's a hint for the IRQ subsystem and doesn't have a meaning within a domain. From DMA mappings point of view, it is effectively the same as RESV_T_RESERVED. When...

...physical IOMMUs. > > For reserved regions, we specify what the driver should do and what the > device should enforce with regard to mapping IOVAs of overlapping regions. > For example, if a device has some virtual address RESV_T_MSI and an other > device has the same virtual address RESV_T_IDENTITY, what should the > driver do? > > I think it should apply the RESV_T_IDENTITY. RESV_T_MSI is just a special > case of RESV_T_RESERVED, it's a hint for the IRQ subsystem and doesn't > have a meaning within a domain. From DMA mappings point of view, it is > effectively the...