aboutsummaryrefslogtreecommitdiff
path: root/qobject/qnull.c
diff options
context:
space:
mode:
authorKunkun Jiang <jiangkunkun@huawei.com>2021-10-27 17:04:06 +0800
committerAlex Williamson <alex.williamson@redhat.com>2021-11-01 12:17:51 -0600
commite4b34708388b20f1ceb55f1d563d8da925a32424 (patch)
tree136e37513ddc010a31d3e3b2bd24f66b6a47aa94 /qobject/qnull.c
parentf36d4fb85f41604038386e1eb4295acd7d372d86 (diff)
downloadqemu-e4b34708388b20f1ceb55f1d563d8da925a32424.zip
qemu-e4b34708388b20f1ceb55f1d563d8da925a32424.tar.gz
qemu-e4b34708388b20f1ceb55f1d563d8da925a32424.tar.bz2
vfio/common: Add a trace point when a MMIO RAM section cannot be mapped
The MSI-X structures of some devices and other non-MSI-X structures may be in the same BAR. They may share one host page, especially in the case of large page granularity, such as 64K. For example, MSIX-Table size of 82599 NIC is 0x30 and the offset in Bar 3(size 64KB) is 0x0. vfio_listener_region_add() will be called to map the remaining range (0x30-0xffff). If host page size is 64KB, it will return early at 'int128_ge((int128_make64(iova), llend))' without any message. Let's add a trace point to inform users like commit 5c08600547c0 ("vfio: Use a trace point when a RAM section cannot be DMA mapped") did. Signed-off-by: Kunkun Jiang <jiangkunkun@huawei.com> Link: https://lore.kernel.org/r/20211027090406.761-3-jiangkunkun@huawei.com Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'qobject/qnull.c')
0 files changed, 0 insertions, 0 deletions