summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/intel-pt-events.py
diff options
context:
space:
mode:
authorAlex Williamson <alex.williamson@redhat.com>2025-03-20 22:41:42 +0300
committerAlex Williamson <alex.williamson@redhat.com>2025-04-14 17:31:45 +0300
commit2bd42b03ab6b04dde1753bd6b38eeca5c70f3941 (patch)
tree0bec6c165250acbc8c11c12800342d3c986a5752 /tools/perf/scripts/python/intel-pt-events.py
parent8ffd015db85fea3e15a77027fda6c02ced4d2444 (diff)
downloadlinux-2bd42b03ab6b04dde1753bd6b38eeca5c70f3941.tar.xz
vfio/pci: Virtualize zero INTx PIN if no pdev->irq
Typically pdev->irq is consistent with whether the device itself supports INTx, where device support is reported via the PIN register. Therefore the PIN register is often already zero if pdev->irq is zero. Recently virtualization of the PIN register was expanded to include the case where the device supports INTx but the platform does not route the interrupt. This is reported by a value of IRQ_NOTCONNECTED on some architectures. Other architectures just report zero for pdev->irq. We already disallow INTx setup if pdev->irq is zero, therefore add this to the PIN register virtualization criteria so that a consistent view is provided to userspace through virtualized config space and ioctls. Reported-by: Shivaprasad G Bhat <sbhat@linux.ibm.com> Link: https://lore.kernel.org/all/174231895238.2295.12586708771396482526.stgit@linux.ibm.com/ Tested-by: Shivaprasad G Bhat <sbhat@linux.ibm.com> Link: https://lore.kernel.org/r/20250320194145.2816379-1-alex.williamson@redhat.com Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/intel-pt-events.py')
0 files changed, 0 insertions, 0 deletions