[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180105101815.0fcbc142@t450s.home>
Date: Fri, 5 Jan 2018 10:18:15 -0700
From: Alex Williamson <alex.williamson@...hat.com>
To: Logan Gunthorpe <logang@...tatee.com>
Cc: Bjorn Helgaas <helgaas@...nel.org>, 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, Stephen Bates <sbates@...thlin.com>,
Christoph Hellwig <hch@....de>, Jens Axboe <axboe@...nel.dk>,
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>
Subject: Re: [PATCH 04/12] pci-p2p: Clear ACS P2P flags for all client
devices
On Fri, 5 Jan 2018 10:10:51 -0700
Logan Gunthorpe <logang@...tatee.com> wrote:
> On 04/01/18 08:33 PM, Alex Williamson wrote:
> > That's exactly what IOMMU groups represent, the smallest set of devices
> > which have DMA isolation from other devices. By poking this hole, the
> > IOMMU group is invalid. We cannot turn off ACS only for a specific
> > device, in order to enable p2p it needs to be disabled at every
> > downstream port between the devices where we want to enable p2p.
> > Depending on the topology, that could mean we're also enabling p2p for
> > unrelated devices. Those unrelated devices might be in active use and
> > the p2p IOVAs now have a different destination which is no longer IOMMU
> > translated.
>
> Oh, so IOMMU groups are created based on the existing hierarchy at boot
> time and not based on the user's needs for isolation?
Yes, IOMMU groups expose the isolation of the system as devices are
discovered. Nothing currently accounts for intentionally decreasing
the isolation between devices. Thanks,
Alex
Powered by blists - more mailing lists