| commit | 62c1b0024b3a4ac95deded14541c428f8fc662fa | |
| author | Joao Martins <joao.m.martins@oracle.com> | |
| Tue, 7 Mar 2023 12:54:44 +0000 (7 12:54 +0000) | ||
| committer | Alex Williamson <alex.williamson@redhat.com> | |
| Tue, 7 Mar 2023 14:20:32 +0000 (7 07:20 -0700) | ||
| tree | 4b6a19acb83519de610577fc6cbba4ee35a69675 | treesnapshot (tar.gz zip) |
| parent | 4ead830848e1f2571ca759ee6734bccd6e2ba3a6 | commitdiff |
vfio/common: Record DMA mapped IOVA ranges
According to the device DMA logging uAPI, IOVA ranges to be logged by
the device must be provided all at once upon DMA logging start.
As preparation for the following patches which will add device dirty
page tracking, keep a record of all DMA mapped IOVA ranges so later they
can be used for DMA logging start.
Signed-off-by: Avihai Horon <avihaih@nvidia.com>
Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Link: https://lore.kernel.org/r/20230307125450.62409-10-joao.m.martins@oracle.com
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
According to the device DMA logging uAPI, IOVA ranges to be logged by
the device must be provided all at once upon DMA logging start.
As preparation for the following patches which will add device dirty
page tracking, keep a record of all DMA mapped IOVA ranges so later they
can be used for DMA logging start.
Signed-off-by: Avihai Horon <avihaih@nvidia.com>
Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Link: https://lore.kernel.org/r/20230307125450.62409-10-joao.m.martins@oracle.com
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
| hw/vfio/common.c | diffblobblamehistory | |
| hw/vfio/trace-events | diffblobblamehistory |