lkml.org 
[lkml]   [2017]   [Jun]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC 2/9] iommu/vt-d: add bind_pasid_table function
On Fri, 23 Jun 2017 11:19:52 -0700
Jacob Pan <jacob.jun.pan@linux.intel.com> wrote:

> On Thu, 22 Jun 2017 16:52:15 -0600
> Alex Williamson <alex.williamson@redhat.com> wrote:
>
> > On Wed, 14 Jun 2017 15:22:56 -0700
> > Jacob Pan <jacob.jun.pan@linux.intel.com> wrote:
> > > +static int intel_iommu_unbind_pasid_table(struct iommu_domain
> > > *domain,
> > > + struct device *dev)
> > > +{
> > > + struct intel_iommu *iommu;
> > > + struct dmar_domain *dmar_domain = to_dmar_domain(domain);
> > > + u8 bus, devfn;
> > > +
> > > + iommu = device_to_iommu(dev, &bus, &devfn);
> > > + if (!iommu)
> > > + return -ENODEV;
> > > + /*
> > > + * REVISIT: we might want to clear the PASID table pointer
> > > + * as part of context clear operation. Currently, it leaves
> > > + * stale data but should be ignored by hardware since
> > > PASIDE
> > > + * is clear.
> > > + */
> > > + /* ATS will be reenabled when remapping is restored */
> > > + pci_disable_ats(to_pci_dev(dev));
> >
> > dev_is_pci()?
> >
> good to check, even thought intel iommu supports PCI only.

That's not true, intel-iommu supports non-PCI devices defined in ACPI
as well. Thanks,

Alex

\
 
 \ /
  Last update: 2017-06-23 20:59    [W:0.062 / U:0.252 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site