It is useful to be able to develop and test p2pdma applications in
virtualized environments. Whitelist the QEMU PCI host bridge emulated
by the default QEMU system for x86_64.

Signed-off-by: Stephen Bates <sbates@raithlin.com>
---
 drivers/pci/p2pdma.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/pci/p2pdma.c b/drivers/pci/p2pdma.c
index 0cb7e0aaba0e..03b41ee0cc72 100644
--- a/drivers/pci/p2pdma.c
+++ b/drivers/pci/p2pdma.c
@@ -442,6 +442,8 @@ static const struct pci_p2pdma_whitelist_entry {
 	{PCI_VENDOR_ID_INTEL,	0x2033, 0},
 	{PCI_VENDOR_ID_INTEL,	0x2020, 0},
 	{PCI_VENDOR_ID_INTEL,	0x09a2, 0},
+	/* QEMU Host Bridge */
+	{PCI_VENDOR_ID_INTEL,	0x29c0, 0},
 	{}
 };
 
-- 
2.43.0


-- 

Cheers

Stephen Bates, PhD.

Hi Stephen,

On 2025-04-14 18:24, Stephen Bates wrote:
> It is useful to be able to develop and test p2pdma applications in
> virtualized environments. Whitelist the QEMU PCI host bridge emulated
> by the default QEMU system for x86_64.

The host bridge is also in real hardware. 82G33 motherboards from c.
2007. Given it's age the real hardware probably doesn't support P2P
transactions, but at the same time it's probably pretty rare and I
wouldn't expect there to be much risk of someone trying and failing a
P2P transaction on such a machine. These things are probably worth
noting in the commit message.

Other than that:

Reviewed-by: Logan Gunthorpe <logang@deltatee.com>

Logan