lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 31 Aug 2018 13:11:48 -0600 From: Logan Gunthorpe <logang@...tatee.com> To: Christian König <christian.koenig@....com>, linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org, linux-nvme@...ts.infradead.org, linux-rdma@...r.kernel.org, linux-nvdimm@...ts.01.org, linux-block@...r.kernel.org Cc: Stephen Bates <sbates@...thlin.com>, Christoph Hellwig <hch@....de>, Keith Busch <keith.busch@...el.com>, Sagi Grimberg <sagi@...mberg.me>, Bjorn Helgaas <bhelgaas@...gle.com>, Jason Gunthorpe <jgg@...lanox.com>, Max Gurtovoy <maxg@...lanox.com>, Dan Williams <dan.j.williams@...el.com>, Jérôme Glisse <jglisse@...hat.com>, Benjamin Herrenschmidt <benh@...nel.crashing.org>, Alex Williamson <alex.williamson@...hat.com>, Jonathan Corbet <corbet@....net> Subject: Re: [PATCH v5 06/13] PCI/P2PDMA: Add P2P DMA driver writer's documentation On 31/08/18 11:38 AM, Christian König wrote: > If you can separate out adding the detection I can take a look adding > this with my DMA-buf P2P efforts. Oh, maybe my previous email wasn't clear, but I'd say that detection is already separate from ZONE_DEVICE. Nothing really needs to be changed. I just think you'll probably want to write you're own function similar to pci_p2pdma_distance that perhaps just takes two pci_devs instead of the list of clients as is needed by nvme-of-like users. To enable a whitelist we just have to handle the case where upstream_bridge_distance() returns -1 and check if the devices are in the same root complex with supported root ports before deciding the transaction is not supported. Logan
Powered by blists - more mailing lists