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 RESEND 03/10] iommu/amd: Initial SVA support for AMD IOMMU
Date: Wed, 23 Aug 2023 11:28:48 -0300 [thread overview]
Message-ID: <ZOYXoMPBQZ5KK9IJ@ziepe.ca> (raw)
In-Reply-To: <20230823140415.729050-4-vasant.hegde@amd.com>
On Wed, Aug 23, 2023 at 02:04:08PM +0000, Vasant Hegde wrote:
> diff --git a/drivers/iommu/amd/sva.c b/drivers/iommu/amd/sva.c
> new file mode 100644
> index 000000000000..c7c7e7cb5414
> --- /dev/null
> +++ b/drivers/iommu/amd/sva.c
> @@ -0,0 +1,299 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Copyright (C) 2023 Advanced Micro Devices, Inc.
> + */
> +
> +#define pr_fmt(fmt) "AMD-Vi: " fmt
> +#define dev_fmt(fmt) pr_fmt(fmt)
> +
> +#include <linux/iommu.h>
> +#include <linux/mm_types.h>
> +#include <linux/mmu_notifier.h>
> +
> +#include "amd_iommu.h"
> +#include "../iommu-sva.h"
> +
> +struct amd_sva_pasid {
> + u32 pasid; /* PASID index */
> + struct mm_struct *mm; /* mm_struct for the faults */
> + struct mmu_notifier mn; /* mmu_notifier handle */
> + struct list_head dev_list; /* List of devices for this pasid */
> +};
> +
> +struct amd_sva_dev {
> + struct device *dev;
> + struct iommu_dev_data *dev_data;
> + struct list_head list;
> + struct rcu_head rcu;
> +};
> +
> +static DEFINE_MUTEX(pasid_mutex);
> +static DEFINE_XARRAY_ALLOC(sva_pasid_array);
> +
> +
> +static int sva_pasid_private_add(u32 pasid, void *priv)
> +{
> + return xa_alloc(&sva_pasid_array, &pasid, priv,
> + XA_LIMIT(pasid, pasid), GFP_ATOMIC);
> +}
> +
> +static void sva_pasid_private_remove(u32 pasid)
> +{
> + xa_erase(&sva_pasid_array, pasid);
> +}
> +
> +static void *sva_pasid_private_find(u32 pasid)
> +{
> + return xa_load(&sva_pasid_array, pasid);
> +}
No PASID stuff in SVA code at all please, all of this is wrong.
The only PASID comes from here, and it should be the only place PASID
shows up:
+int amd_iommu_set_dev_pasid(struct iommu_domain *domain,
+ struct device *dev, ioasid_t pasid)
+{
> +static int sva_bind_mm(struct device *dev, struct mm_struct *mm)
> +{
> + struct amd_sva_pasid *sva_pasid;
> + struct amd_sva_dev *sva_dev;
> + struct iommu_dev_data *dev_data = dev_iommu_priv_get(dev);
> + int ret = -EINVAL;
> +
> + sva_dev = sva_dev_alloc(dev);
> + if (!sva_dev)
> + return ret;
> +
> + sva_pasid = sva_pasid_private_find(mm->pasid);
> + if (!sva_pasid) {
> + sva_pasid = sva_pasid_alloc(mm);
> + if (!sva_pasid)
> + goto out_sva_dev;
No per-PASID struct. AMD enablement should go after this series:
https://lore.kernel.org/linux-iommu/20230808074944.7825-1-tina.zhang@intel.com/
Put the mmu_notifier directly into the protection_domain. Assume you
have a single protection_domain per mm.
Also amd_sva_dev is not appropriate, the list of PASIDs (and masters)
a domain is associated with is part of the generic PASID support in
the protection_domain itself.
These details would be clearer if you start from enabling PASID
support for an UNMANAGED domain.
SVA should be a tiny incremental from that which simply calls the
same invalidation and manages the mmu notifier.
> +static struct amd_sva_dev *sva_dev_alloc(struct device *dev)
> +{
> + struct amd_sva_dev *sva_dev;
> + struct iommu_dev_data *dev_data = dev_iommu_priv_get(dev);
> +
> + sva_dev = kzalloc(sizeof(*sva_dev), GFP_KERNEL);
> + if (!sva_dev)
> + return NULL;
> +
> + sva_dev->dev = dev;
> + sva_dev->dev_data = dev_data;
> + init_rcu_head(&sva_dev->rcu);
> +
> + return sva_dev;
> +}
> +
> +static inline void sva_dev_free(struct amd_sva_dev *sva_dev)
> +{
> + kfree_rcu(sva_dev, rcu);
> +}
> +
> +static void sva_mn_invalidate_range(struct mmu_notifier *mn,
> + struct mm_struct *mm,
> + unsigned long start, unsigned long end)
> +{
> + struct amd_sva_pasid *sva_pasid;
> + struct amd_sva_dev *sva_dev;
> +
> + rcu_read_lock();
> +
> + sva_pasid = container_of(mn, struct amd_sva_pasid, mn);
> + if (!sva_pasid) {
> + rcu_read_unlock();
> + return;
> + }
> +
> + list_for_each_entry_rcu(sva_dev, &sva_pasid->dev_list, list) {
> + if ((start ^ (end - 1)) < PAGE_SIZE)
> + amd_iommu_flush_page(sva_dev->dev_data->domain, sva_pasid->pasid, start);
> + else
> + amd_iommu_flush_tlb(sva_dev->dev_data->domain, sva_pasid->pasid);
> + }
SVA invalidation should be the same as normal PASID invalidation. You
need to track the list of PASIDs a protection_domain is associated
with in the protection domain itself, not in special SVA code. Don't
repeat the SMMU mistakes please.
Use container_of(mn) to get back to the SVA protection domain and then
you can access the protection domains list of PASIDs & masters.
> +static int sva_bind_mm(struct device *dev, struct mm_struct *mm)
> +{
> + struct amd_sva_pasid *sva_pasid;
> + struct amd_sva_dev *sva_dev;
> + struct iommu_dev_data *dev_data = dev_iommu_priv_get(dev);
> + int ret = -EINVAL;
> +
> + sva_dev = sva_dev_alloc(dev);
> + if (!sva_dev)
> + return ret;
> +
> + sva_pasid = sva_pasid_private_find(mm->pasid);
> + if (!sva_pasid) {
> + sva_pasid = sva_pasid_alloc(mm);
> + if (!sva_pasid)
> + goto out_sva_dev;
> +
> + ret = sva_pasid_private_add(sva_pasid->pasid, sva_pasid);
> + if (ret)
> + goto out_sva_pasid;
> +
> + ret = amd_iommu_set_gcr3(dev_data, sva_pasid->pasid,
> + iommu_virt_to_phys(sva_pasid->mm->pgd));
> + if (ret)
> + goto out_pasid_remove;
> +
> + ret = mmu_notifier_register(&sva_pasid->mn, mm);
> + if (ret)
> + goto out_clear_gcr3;
> + }
The mmu_notifier should be setup when the domain is allocated, not
during bind.
This is an issue we need to fix in the core code :(
> +void amd_iommu_remove_dev_pasid(struct device *dev, ioasid_t pasid)
> +{
> + struct iommu_domain *domain;
> +
> + if (pasid == 0 || pasid >= dev->iommu->max_pasids)
> + return;
We should probably have the core code pass in the old domain to this
function, it is looking more like a mistake we didn't do that.
> +
> + /* Get SVA domain */
> + domain = iommu_get_domain_for_dev_pasid(dev, pasid, 0);
> + if (!domain)
> + return;
> +
> + switch (domain->type) {
> + case IOMMU_DOMAIN_SVA:
> + /* Ensure that all queued faults have been processed */
> + iopf_queue_flush_dev(dev);
> +
> + mutex_lock(&pasid_mutex);
> + sva_unbind_mm(dev, pasid);
> + mutex_unlock(&pasid_mutex);
SVA should not be special for detach, this should all be generic code.
The mmu notifier is freed during SVA domain dealloc.
Jason
next prev parent reply other threads:[~2023-08-23 14:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 14:04 [PATCH RESEND 00/10] iommu/amd: SVA Support (Part 4) - SVA and IOPF Vasant Hegde
2023-08-23 14:04 ` [PATCH RESEND 01/10] iommu/amd: Rename amd_iommu_v2_supported() as amd_iommu_sva_supported() Vasant Hegde
2023-08-23 14:04 ` [PATCH RESEND 02/10] iommu/amd: Add support for enabling/disabling IOMMU features Vasant Hegde
2023-08-23 14:04 ` [PATCH RESEND 03/10] iommu/amd: Initial SVA support for AMD IOMMU Vasant Hegde
2023-08-23 14:28 ` Jason Gunthorpe [this message]
2023-08-28 10:39 ` Vasant Hegde
2023-08-30 17:07 ` Jason Gunthorpe
2023-09-05 6:18 ` Vasant Hegde
2023-09-05 12:26 ` Jason Gunthorpe
2023-09-05 14:39 ` Vasant Hegde
2023-09-05 18:14 ` Jason Gunthorpe
2023-09-11 12:16 ` Vasant Hegde
2023-09-11 12:41 ` Jason Gunthorpe
2023-08-23 14:04 ` [PATCH RESEND 04/10] iommu/amd: Add support to enable/disable SVA feature Vasant Hegde
2023-08-23 15:28 ` Jason Gunthorpe
2023-08-28 10:45 ` Vasant Hegde
2023-08-30 17:09 ` Jason Gunthorpe
2023-08-30 19:00 ` Vasant Hegde
2023-08-30 23:46 ` Jason Gunthorpe
2023-09-07 7:15 ` Vasant Hegde
2023-09-07 12:04 ` Jason Gunthorpe
2023-08-23 14:04 ` [PATCH RESEND 05/10] iommu/amd: Move PPR-related functions into ppr.c Vasant Hegde
2023-08-23 14:04 ` [PATCH RESEND 06/10] iommu/amd: Define per-IOMMU iopf_queue Vasant Hegde
2023-08-23 14:04 ` [PATCH RESEND 07/10] iommu/amd: Add support for page response Vasant Hegde
2023-08-23 14:04 ` [PATCH RESEND 08/10] iommu/amd: Add support for add/remove device for IOPF Vasant Hegde
2023-08-23 15:33 ` Jason Gunthorpe
2023-08-30 14:34 ` Vasant Hegde
2023-08-23 14:04 ` [PATCH RESEND 09/10] iommu/amd: Add IO page fault notifier handler Vasant Hegde
2023-08-23 14:04 ` [PATCH RESEND 10/10] iommu/amd: Introduce logic to enable/disable IOPF Vasant Hegde
2023-08-23 15:36 ` 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=ZOYXoMPBQZ5KK9IJ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox