From: Yinghai Lu <yhlu.kernel@gmail.com>
To: Fenghua Yu <fenghua.yu@intel.com>,
jbarnes@virtuousgeek.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Cc: David Woodhouse <dwmw2@infradead.org>,
Joerg Roedel <joro@8bytes.org>,
Francois Isabelle <Francois.Isabelle@ca.kontron.com>,
iommu <iommu@lists.linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCIe hot plug for Intel iommu
Date: Thu, 22 Oct 2009 00:07:11 -0700 [thread overview]
Message-ID: <86802c440910220007s5881653o5fbbc810523b18fe@mail.gmail.com> (raw)
In-Reply-To: <20091006182346.GA22770@linux-os.sc.intel.com>
On Tue, Oct 6, 2009 at 11:23 AM, Fenghua Yu <fenghua.yu@intel.com> wrote:
> To support PCIe hot plug in IOMMU, we register a notifier to respond to device
> change action.
>
> When the notifier gets BUS_NOTIFY_UNBOUND_DRIVER, it removes the device from its
> DMAR domain.
>
> A hot added device will be added into an IOMMU domain when it first does IOMMU
> op. So there is no need to add more code for hot add.
>
> Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
>
> ---
>
> intel-iommu.c | 29 +++++++++++++++++++++++++++++
> 1 files changed, 29 insertions(+)
>
> diff --git a/drivers/pci/intel-iommu.c b/drivers/pci/intel-iommu.c
> index 855dd7c..d8b8cfc 100644
> --- a/drivers/pci/intel-iommu.c
> +++ b/drivers/pci/intel-iommu.c
> @@ -3193,6 +3193,33 @@ static int __init init_iommu_sysfs(void)
> }
> #endif /* CONFIG_PM */
>
> +/*
> + * Here we only respond to action of unbound device from driver.
> + *
> + * Added device is not attached to its DMAR domain here yet. That will happen
> + * when mapping the device to iova.
> + */
> +static int device_notifier(struct notifier_block *nb,
> + unsigned long action, void *data)
> +{
> + struct device *dev = data;
> + struct pci_dev *pdev = to_pci_dev(dev);
> + struct dmar_domain *domain;
> +
> + domain = find_domain(pdev);
> + if (!domain)
> + return 0;
> +
> + if (action == BUS_NOTIFY_UNBOUND_DRIVER && !iommu_pass_through)
> + domain_remove_one_dev_info(domain, pdev);
> +
> + return 0;
> +}
> +
> +static struct notifier_block device_nb = {
> + .notifier_call = device_notifier,
> +};
> +
> int __init intel_iommu_init(void)
> {
> int ret = 0;
> @@ -3245,6 +3272,8 @@ int __init intel_iommu_init(void)
>
> register_iommu(&intel_iommu_ops);
>
> + bus_register_notifier(&pci_bus_type, &device_nb);
> +
> return 0;
> }
>
it seems this one should be get into 2.6.32....and .stable
otherwise second hot plug in the same pcie slot will not work with dma.
YH
prev parent reply other threads:[~2009-10-22 7:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <72D8A09E39A89147BE9CFBB6F0C73C306073445396@rrsmsx501.amr.corp.intel.com>
[not found] ` <6E2431EDEB6AE64F827F8A1B0D0DA1A603C322CF@azsmsx501.amr.corp.intel.com>
[not found] ` <72D8A09E39A89147BE9CFBB6F0C73C30607344552A@rrsmsx501.amr.corp.intel.com>
2009-10-02 21:18 ` [PATCH 2/2] pciehp_driver.c: PCIe hot plug for Intel iommu - call IOMMU API in hot remove Fenghua Yu
2009-10-02 21:50 ` Joerg Roedel
2009-10-03 0:01 ` Fenghua Yu
2009-10-06 18:23 ` [PATCH] PCIe hot plug for Intel iommu Fenghua Yu
2009-10-22 7:07 ` Yinghai Lu [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=86802c440910220007s5881653o5fbbc810523b18fe@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=Francois.Isabelle@ca.kontron.com \
--cc=dwmw2@infradead.org \
--cc=fenghua.yu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
/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®