All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: iommu@lists.linux.dev, joro@8bytes.org,
	suravee.suthikulpanit@amd.com, wei.huang2@amd.com,
	jsnitsel@redhat.com
Subject: Re: [PATCH v2 11/11] iommu/amd: Introduce logic to enable/disable IOPF
Date: Mon, 18 Sep 2023 09:45:05 -0300	[thread overview]
Message-ID: <20230918124505.GC13795@ziepe.ca> (raw)
In-Reply-To: <57dfeefb-5a21-3e18-46f1-851de56a3037@amd.com>

On Fri, Sep 15, 2023 at 01:56:54PM +0530, Vasant Hegde wrote:

> >> +static int amd_iommu_iopf_update(struct device *dev, bool enable)
> >> +{
> >> +	unsigned long flags;
> >> +	int ret;
> >> +	struct pci_dev *pdev = dev_is_pci(dev) ? to_pci_dev(dev) : NULL;
> >> +	struct amd_iommu *iommu = get_amd_iommu_from_dev(dev);
> >> +	struct iommu_dev_data *dev_data = dev_iommu_priv_get(dev);
> >> +	struct protection_domain *pdom = amd_iommu_get_pdomain(dev);
> >> +
> >> +	if (!pdev || !iommu || !dev_data)
> >> +		return -EINVAL;
> >> +
> >> +	spin_lock_irqsave(&pdom->lock, flags);
> >> +
> >> +	if (enable) {
> >> +		ret = amd_iommu_iopf_add_device(iommu, dev);
> >> +		if (ret)
> >> +			goto out;
> >> +
> >> +		dev_data->ppr = true;
> >> +	} else {
> >> +		ret = amd_iommu_iopf_remove_device(iommu, dev);
> >> +		dev_data->ppr = false;
> >> +	}
> >> +
> >> +	amd_iommu_domain_update(pdom);
> >> +
> >> +out:
> >> +	spin_unlock_irqrestore(&pdom->lock, flags);
> >> +	return ret;
> >> +}
> > 
> > Same remarks as for the SVA, this is in the wrong place.
> > 
> > iopf_queue_add_device() should be done when a PRI enabled domain is
> > attached to a device, not in feature things. I also want to remove
> > these too once ARM is fixed..
> 
> You mean we should do this during first device/pasid bind time?

Yes, when a PRI capable domain is first attached the PRI stuff should
be setup. SVA is a PRI capable domain type, but we will have more..

> > amd_iommu_get_pdomain() has improper locking, it needs to hold some
> > kind of dev_data lock to access dev_data->domain. (and really this
> > would all be clearer if it was just written dev_data->domain instead
> > of the redundant function)
> 
> It helps to get iommu from device structure. Its useful and we want to use it
> other places as well.

As I said, it seems obfuscating as to how the locking needs to work as
you must hold a lock while using dev_data->domain. In some cases that
can be the core code's group mutex, but that doesn't always work..

Jason

  reply	other threads:[~2023-09-18 12:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 12:10 [PATCH v2 00/11] iommu/amd: SVA Support (Part 4) - SVA and IOPF Vasant Hegde
2023-09-11 12:10 ` [PATCH v2 01/11] iommu/amd: Rename amd_iommu_v2_supported() as amd_iommu_sva_supported() Vasant Hegde
2023-09-11 12:10 ` [PATCH v2 02/11] iommu/amd: Do not override PASID entry in GCR3 table Vasant Hegde
2023-09-11 12:10 ` [PATCH v2 03/11] iommu/amd: Add support for enabling/disabling IOMMU features Vasant Hegde
2023-09-11 12:10 ` [PATCH v2 04/11] iommu/amd: Initial SVA support for AMD IOMMU Vasant Hegde
2023-09-12 16:47   ` Jason Gunthorpe
2023-09-15  8:50     ` Vasant Hegde
2023-09-18 12:53       ` Jason Gunthorpe
2023-10-13 15:52         ` Vasant Hegde
2023-10-13 15:58           ` Jason Gunthorpe
2023-09-11 12:10 ` [PATCH v2 05/11] iommu/amd: Add support to enable/disable PASID feature Vasant Hegde
2023-09-12 16:57   ` Jason Gunthorpe
2023-09-15  8:57     ` Vasant Hegde
2023-09-11 12:10 ` [PATCH v2 06/11] iommu/amd: Move PPR-related functions into ppr.c Vasant Hegde
2023-09-11 12:10 ` [PATCH v2 07/11] iommu/amd: Define per-IOMMU iopf_queue Vasant Hegde
2023-09-12 16:59   ` Jason Gunthorpe
2023-09-15 13:48     ` Vasant Hegde
2023-09-11 12:10 ` [PATCH v2 08/11] iommu/amd: Add support for page response Vasant Hegde
2023-09-11 12:10 ` [PATCH v2 09/11] iommu/amd: Add support for add/remove device for IOPF Vasant Hegde
2023-09-11 12:10 ` [PATCH v2 10/11] iommu/amd: Add IO page fault notifier handler Vasant Hegde
2023-09-12 18:46   ` Jason Gunthorpe
2023-09-13  4:19     ` Baolu Lu
2023-09-15  8:15     ` Vasant Hegde
2023-09-11 12:10 ` [PATCH v2 11/11] iommu/amd: Introduce logic to enable/disable IOPF Vasant Hegde
2023-09-12 16:32   ` Jason Gunthorpe
2023-09-15  8:26     ` Vasant Hegde
2023-09-18 12:45       ` Jason Gunthorpe [this message]
2023-10-10 14:53         ` Vasant Hegde
2023-10-10 15:04           ` Jason Gunthorpe
2023-09-12 18:48 ` [PATCH v2 00/11] iommu/amd: SVA Support (Part 4) - SVA and IOPF Jason Gunthorpe

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=20230918124505.GC13795@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=jsnitsel@redhat.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=vasant.hegde@amd.com \
    --cc=wei.huang2@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.