qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Don Dutile <ddutile@redhat.com>
Cc: aafabbri@cisco.com, kvm@vger.kernel.org, B07421@freescale.com,
	aik@ozlabs.ru, konrad.wilk@oracle.com, linux-pci@vger.kernel.org,
	agraf@suse.de, qemu-devel@nongnu.org, chrisw@sous-sol.org,
	B08248@freescale.com, iommu@lists.linux-foundation.org,
	gregkh@linuxfoundation.org, avi@redhat.com, joerg.roedel@amd.com,
	bhelgaas@google.com, benve@cisco.com, dwmw2@infradead.org,
	linux-kernel@vger.kernel.org, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH v2 03/13] iommu: IOMMU groups for VT-d and AMD-Vi
Date: Thu, 24 May 2012 15:49:28 -0600	[thread overview]
Message-ID: <1337896168.4714.39.camel@ul30vt> (raw)
In-Reply-To: <4FBEA18F.1040607@redhat.com>

On Thu, 2012-05-24 at 17:01 -0400, Don Dutile wrote:
> On 05/22/2012 01:04 AM, Alex Williamson wrote:
> > Add back group support for AMD&  Intel.  amd_iommu already tracks
> > devices and has init and uninit routines to manage groups.
> > intel-iommu does this on the fly, so we make use of the notifier
> > support built into iommu groups to create and remove groups.
> >
> > Signed-off-by: Alex Williamson<alex.williamson@redhat.com>
> > ---
> >
> >   drivers/iommu/amd_iommu.c   |   28 +++++++++++++++++++++++++-
> >   drivers/iommu/intel-iommu.c |   46 +++++++++++++++++++++++++++++++++++++++++++
> >   2 files changed, 73 insertions(+), 1 deletions(-)
> >
> > diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
> > index 32c00cd..b7e5ddf 100644
> > --- a/drivers/iommu/amd_iommu.c
> > +++ b/drivers/iommu/amd_iommu.c
> > @@ -256,9 +256,11 @@ static bool check_device(struct device *dev)
> >
> >   static int iommu_init_device(struct device *dev)
> >   {
> > -	struct pci_dev *pdev = to_pci_dev(dev);
> > +	struct pci_dev *dma_pdev, *pdev = to_pci_dev(dev);
> >   	struct iommu_dev_data *dev_data;
> > +	struct iommu_group *group;
> >   	u16 alias;
> > +	int ret;
> >
> >   	if (dev->archdata.iommu)
> >   		return 0;
> > @@ -279,8 +281,30 @@ static int iommu_init_device(struct device *dev)
> >   			return -ENOTSUPP;
> >   		}
> >   		dev_data->alias_data = alias_data;
> > +
> > +		dma_pdev = pci_get_bus_and_slot(alias>>  8, alias&  0xff);
> > +	} else
> > +		dma_pdev = pdev;
> > +
> > +	if (!pdev->is_virtfn&&  PCI_FUNC(pdev->devfn)&&  iommu_group_mf&&
> > +	    pdev->hdr_type == PCI_HEADER_TYPE_NORMAL)
> > +		dma_pdev = pci_get_slot(pdev->bus,
> > +					PCI_DEVFN(PCI_SLOT(pdev->devfn), 0));
> > +
> > +	group = iommu_group_get(&dma_pdev->dev);
> > +	if (!group) {
> > +		group = iommu_group_alloc();
> > +		if (IS_ERR(group))
> > +			return PTR_ERR(group);
> >   	}
> >
> > +	ret = iommu_group_add_device(group, dev);
> > +
> > +	iommu_group_put(group);
> > +
> do you want to do a put if there is a failure in the iommu_group_add_device()?

Yes, this was intentional.  iommu_group_alloc() adds a reference to the
group it returns so that it doesn't disappear while we're working on it
(documented in iommu.c).  iommu_group_get() also gets a reference.  So
this put will free the group if it was new or just drop the reference if
existing.  Thanks,

Alex

> > +	if (ret)
> > +		return ret;
> > +
> >   	if (pci_iommuv2_capable(pdev)) {
> >   		struct amd_iommu *iommu;
> >
> > @@ -309,6 +333,8 @@ static void iommu_ignore_device(struct device *dev)
> >
> >   static void iommu_uninit_device(struct device *dev)
> >   {
> > +	iommu_group_remove_device(dev);
> > +
> >   	/*
> >   	 * Nothing to do here - we keep dev_data around for unplugged devices
> >   	 * and reuse it when the device is re-plugged - not doing so would
> > diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c
> > index d4a0ff7..e63b33b 100644
> > --- a/drivers/iommu/intel-iommu.c
> > +++ b/drivers/iommu/intel-iommu.c
> > @@ -4087,6 +4087,50 @@ static int intel_iommu_domain_has_cap(struct iommu_domain *domain,
> >   	return 0;
> >   }
> >
> > +static int intel_iommu_add_device(struct device *dev)
> > +{
> > +	struct pci_dev *pdev = to_pci_dev(dev);
> > +	struct pci_dev *bridge, *dma_pdev = pdev;
> > +	struct iommu_group *group;
> > +	int ret;
> > +
> > +	if (!device_to_iommu(pci_domain_nr(pdev->bus),
> > +			     pdev->bus->number, pdev->devfn))
> > +		return -ENODEV;
> > +
> > +	bridge = pci_find_upstream_pcie_bridge(pdev);
> > +	if (bridge) {
> > +		if (pci_is_pcie(bridge))
> > +			dma_pdev = pci_get_domain_bus_and_slot(
> > +						pci_domain_nr(pdev->bus),
> > +						bridge->subordinate->number, 0);
> > +		else
> > +			dma_pdev = bridge;
> > +	}
> > +
> > +	if (!pdev->is_virtfn&&  PCI_FUNC(pdev->devfn)&&  iommu_group_mf&&
> > +	    pdev->hdr_type == PCI_HEADER_TYPE_NORMAL)
> > +		dma_pdev = pci_get_slot(pdev->bus,
> > +					PCI_DEVFN(PCI_SLOT(pdev->devfn), 0));
> > +
> > +	group = iommu_group_get(&dma_pdev->dev);
> > +	if (!group) {
> > +		group = iommu_group_alloc();
> > +		if (IS_ERR(group))
> > +			return PTR_ERR(group);
> > +	}
> > +
> > +	ret = iommu_group_add_device(group, dev);
> > +
> ditto.
> > +	iommu_group_put(group);
> > +	return ret;
> > +}
> > +
> > +static void intel_iommu_remove_device(struct device *dev)
> > +{
> > +	iommu_group_remove_device(dev);
> > +}
> > +
> >   static struct iommu_ops intel_iommu_ops = {
> >   	.domain_init	= intel_iommu_domain_init,
> >   	.domain_destroy = intel_iommu_domain_destroy,
> > @@ -4096,6 +4140,8 @@ static struct iommu_ops intel_iommu_ops = {
> >   	.unmap		= intel_iommu_unmap,
> >   	.iova_to_phys	= intel_iommu_iova_to_phys,
> >   	.domain_has_cap = intel_iommu_domain_has_cap,
> > +	.add_device	= intel_iommu_add_device,
> > +	.remove_device	= intel_iommu_remove_device,
> >   	.pgsize_bitmap	= INTEL_IOMMU_PGSIZES,
> >   };
> >
> >
> 

  reply	other threads:[~2012-05-24 21:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22  5:04 [Qemu-devel] [PATCH v2 00/13] IOMMU Groups + VFIO Alex Williamson
2012-05-22  5:04 ` [Qemu-devel] [PATCH v2 01/13] driver core: Add iommu_group tracking to struct device Alex Williamson
2012-05-22  5:04 ` [Qemu-devel] [PATCH v2 02/13] iommu: IOMMU Groups Alex Williamson
2012-05-22  5:04 ` [Qemu-devel] [PATCH v2 03/13] iommu: IOMMU groups for VT-d and AMD-Vi Alex Williamson
2012-05-24 21:01   ` Don Dutile
2012-05-24 21:49     ` Alex Williamson [this message]
2012-05-22  5:05 ` [Qemu-devel] [PATCH v2 04/13] pci: Add PCI DMA source ID quirk Alex Williamson
2012-05-22  5:05 ` [Qemu-devel] [PATCH v2 05/13] pci: Add ACS validation utility Alex Williamson
2012-05-24 21:30   ` Don Dutile
2012-05-24 22:35     ` Alex Williamson
2012-05-22  5:05 ` [Qemu-devel] [PATCH v2 06/13] iommu: Make use of DMA quirking and ACS enabled check for groups Alex Williamson
2012-05-22  5:05 ` [Qemu-devel] [PATCH v2 07/13] vfio: VFIO core Alex Williamson
2012-05-22  5:05 ` [Qemu-devel] [PATCH v2 08/13] vfio: Add documentation Alex Williamson
2012-05-22  5:05 ` [Qemu-devel] [PATCH v2 09/13] vfio: x86 IOMMU implementation Alex Williamson
2012-05-24 21:38   ` Don Dutile
2012-05-24 22:46     ` Alex Williamson
2012-05-25 15:22       ` Don Dutile
2012-05-22  5:05 ` [Qemu-devel] [PATCH v2 10/13] pci: export pci_user functions for use by other drivers Alex Williamson
2012-05-22  5:05 ` [Qemu-devel] [PATCH v2 11/13] pci: Create common pcibios_err_to_errno Alex Williamson
2012-05-22  5:05 ` [Qemu-devel] [PATCH v2 12/13] pci: Misc pci_reg additions Alex Williamson
2012-05-24 21:49   ` Don Dutile
2012-05-24 22:17     ` Alex Williamson
2012-05-22  5:06 ` [Qemu-devel] [PATCH v2 13/13] vfio: Add PCI device driver Alex Williamson
2012-05-24 21:56 ` [Qemu-devel] [PATCH v2 00/13] IOMMU Groups + VFIO Don Dutile

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=1337896168.4714.39.camel@ul30vt \
    --to=alex.williamson@redhat.com \
    --cc=B07421@freescale.com \
    --cc=B08248@freescale.com \
    --cc=aafabbri@cisco.com \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=avi@redhat.com \
    --cc=benve@cisco.com \
    --cc=bhelgaas@google.com \
    --cc=chrisw@sous-sol.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=ddutile@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joerg.roedel@amd.com \
    --cc=konrad.wilk@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).