From: David Woodhouse <dwmw2@infradead.org>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Francois Isabelle <Francois.Isabelle@ca.kontron.com>,
Weidong Han <weidong.han@intel.com>,
iommu@lists.linux-foundation.org,
Grant Grundler <grundler@parisc-linux.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] intel-iommu: PCIe hot plug for Intel iommu - IOMMU API
Date: Mon, 05 Oct 2009 07:59:30 +0100 [thread overview]
Message-ID: <1254725970.3277.3096.camel@macbook.infradead.org> (raw)
In-Reply-To: <20091002211826.GA11326@linux-os.sc.intel.com>
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
prev parent reply other threads:[~2009-10-05 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` Fenghua Yu
2009-10-05 6:59 ` David Woodhouse [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1254725970.3277.3096.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=Francois.Isabelle@ca.kontron.com \
--cc=fenghua.yu@intel.com \
--cc=grundler@parisc-linux.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=weidong.han@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®