28 Oct
2024
28 Oct
'24
2:35 a.m.
From: Jason Gunthorpe jgg@nvidia.com Sent: Friday, October 25, 2024 11:43 PM
On Fri, Oct 25, 2024 at 08:34:05AM +0000, Tian, Kevin wrote:
The vIOMMU object should be seen as a slice of a physical IOMMU
instance
that is passed to or shared with a VM. That can be some HW/SW
resources:
- Security namespace for guest owned ID, e.g. guest-controlled cache
tags
- Access to a sharable nesting parent pagetable across physical IOMMUs
- Virtualization of various platforms IDs, e.g. RIDs and others
- Delivery of paravirtualized invalidation
- Direct assigned invalidation queues
- Direct assigned interrupts
- Non-affiliated event reporting
sorry no idea about 'non-affiliated event'. Can you elaborate?
This would be an even that is not a connected to a device
For instance a CMDQ experienced a problem.
Okay, then 'non-device-affiliated' is probably clearer.