search for: resv_mem_t_abort

...est. I am considering recoverable faults as the end goal, but reporting unrecoverable faults should use the same queue, with slightly different fields and no need for the driver to reply to the device. > 2.6.8.2 Property RESV_MEM > > I'm not immediately clear when VIRTIO_IOMMU_PROBE_RESV_MEM_T_ABORT > should be explicitly reported. Is there any real example on bare metal IOMMU? > usually reserved memory is reported to CPU through other method (e.g. e820 > on x86 platform). Of course MSI is a special case which is covered by BYPASS > and MSI flag... If yes, maybe you can also inclu...

...est. I am considering recoverable faults as the end goal, but reporting unrecoverable faults should use the same queue, with slightly different fields and no need for the driver to reply to the device. > 2.6.8.2 Property RESV_MEM > > I'm not immediately clear when VIRTIO_IOMMU_PROBE_RESV_MEM_T_ABORT > should be explicitly reported. Is there any real example on bare metal IOMMU? > usually reserved memory is reported to CPU through other method (e.g. e820 > on x86 platform). Of course MSI is a special case which is covered by BYPASS > and MSI flag... If yes, maybe you can also inclu...

...older for now? Though same mechanism can be reused, it's an essential part to make virtio-iommu architecture complete even before talking support for recoverable faults. :-) > > > 2.6.8.2 Property RESV_MEM > > > > I'm not immediately clear when > VIRTIO_IOMMU_PROBE_RESV_MEM_T_ABORT > > should be explicitly reported. Is there any real example on bare metal > IOMMU? > > usually reserved memory is reported to CPU through other method (e.g. > e820 > > on x86 platform). Of course MSI is a special case which is covered by > BYPASS > > and MSI flag.....