* [PATCH 1/2] intel-iommu: PCIe hot plug for Intel iommu - IOMMU API [not found] ` <C2866F9FC4CB034EB51A633DF168598605E2D2EE@ssbarcelone> @ 2009-10-02 21:18 ` Fenghua Yu 2009-10-05 6:59 ` David Woodhouse 0 siblings, 1 reply; 2+ messages in thread From: Fenghua Yu @ 2009-10-02 21:18 UTC (permalink / raw) To: David Woodhouse, Jesse Barnes, Francois Isabelle Cc: Weidong Han, iommu, Grant Grundler, linux-kernel We expand existing IOMMU API iommu_detach_device for PCIe hot remove. We don't need IOMMU API for hot add. Signed-off-by: Fenghua Yu <fenghua.yu@intel.com> --- drivers/pci/intel-iommu.c | 13 ++++++++++++- 1 files changed, 12 insertions(+), 1 deletion(-) diff --git a/drivers/pci/intel-iommu.c b/drivers/pci/intel-iommu.c index 855dd7c..5c12283 100644 --- a/drivers/pci/intel-iommu.c +++ b/drivers/pci/intel-iommu.c @@ -3559,9 +3559,20 @@ static int intel_iommu_attach_device(struct iommu_domain *domain, static void intel_iommu_detach_device(struct iommu_domain *domain, struct device *dev) { - struct dmar_domain *dmar_domain = domain->priv; + struct dmar_domain *dmar_domain; struct pci_dev *pdev = to_pci_dev(dev); + /* If domain=NULL, we'll find a valid domain for the device.*/ + if (!domain) { + dmar_domain = find_domain(pdev); + if (!dmar_domain) { + printk(KERN_ERR "Can not find IOMMU domain for %s\n", + pci_name(pdev)); + return; + } + } else + dmar_domain = domain->priv; + domain_remove_one_dev_info(dmar_domain, pdev); } ^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH 1/2] intel-iommu: PCIe hot plug for Intel iommu - IOMMU API 2009-10-02 21:18 ` [PATCH 1/2] intel-iommu: PCIe hot plug for Intel iommu - IOMMU API Fenghua Yu @ 2009-10-05 6:59 ` David Woodhouse 0 siblings, 0 replies; 2+ messages in thread From: David Woodhouse @ 2009-10-05 6:59 UTC (permalink / raw) To: Fenghua Yu Cc: Jesse Barnes, Francois Isabelle, Weidong Han, iommu, Grant Grundler, linux-kernel On Fri, 2009-10-02 at 14:18 -0700, Fenghua Yu wrote: > We expand existing IOMMU API iommu_detach_device for PCIe hot remove. We don't > need IOMMU API for hot add. I think this could do with more explanation. A hot remove will cause detach_device() to be called with a NULL domain parameter? Surely we shouldn't be printing an error with KERN_ERR just because such a device hasn't been used for DMA before it was removed? > Signed-off-by: Fenghua Yu <fenghua.yu@intel.com> > --- > > drivers/pci/intel-iommu.c | 13 ++++++++++++- > 1 files changed, 12 insertions(+), 1 deletion(-) > > diff --git a/drivers/pci/intel-iommu.c b/drivers/pci/intel-iommu.c > index 855dd7c..5c12283 100644 > --- a/drivers/pci/intel-iommu.c > +++ b/drivers/pci/intel-iommu.c > @@ -3559,9 +3559,20 @@ static int intel_iommu_attach_device(struct iommu_domain *domain, > static void intel_iommu_detach_device(struct iommu_domain *domain, > struct device *dev) > { > - struct dmar_domain *dmar_domain = domain->priv; > + struct dmar_domain *dmar_domain; > struct pci_dev *pdev = to_pci_dev(dev); > > + /* If domain=NULL, we'll find a valid domain for the device.*/ > + if (!domain) { > + dmar_domain = find_domain(pdev); > + if (!dmar_domain) { > + printk(KERN_ERR "Can not find IOMMU domain for %s\n", > + pci_name(pdev)); > + return; > + } > + } else > + dmar_domain = domain->priv; > + > domain_remove_one_dev_info(dmar_domain, pdev); > } > -- dwmw2 ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-10-05 7:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <A6AD88C3F2289247BE726C37303E1EB8BC06E356@orsmsx505.amr.corp.intel.com>
[not found] ` <715D42877B251141A38726ABF5CABF2C05505A7433@pdsmsx503.ccr.corp.intel.com>
[not found] ` <C2866F9FC4CB034EB51A633DF168598605E2D2EE@ssbarcelone>
2009-10-02 21:18 ` [PATCH 1/2] intel-iommu: PCIe hot plug for Intel iommu - IOMMU API Fenghua Yu
2009-10-05 6:59 ` David Woodhouse
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox