All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Michael Shavit <mshavit@google.com>
Cc: iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, will@kernel.org,
	nicolinc@nvidia.com, tina.zhang@intel.com,
	jean-philippe@linaro.org, robin.murphy@arm.com
Subject: Re: [RFC PATCH v1 1/8] iommu/arm-smmu-v3: Add list of installed_smmus
Date: Thu, 17 Aug 2023 16:05:55 -0300	[thread overview]
Message-ID: <ZN5vk9cVp0j0jd8T@nvidia.com> (raw)
In-Reply-To: <20230818021629.RFC.v1.1.I9df3dec9e33165276eba8e2dbf7025bfee286d90@changeid>

On Fri, Aug 18, 2023 at 02:16:23AM +0800, Michael Shavit wrote:
> diff --git a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
> index 83d2790b701e7..a9202d2045537 100644
> --- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
> +++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
> @@ -690,12 +690,20 @@ struct arm_smmu_stream {
>  	struct rb_node			node;
>  };
>  
> +/* List of smmu devices that a domain is installed to */
> +struct arm_smmu_installed_smmu {
> +	struct list_head	list;

'installed_smmus_item'

> +	/* List of masters that the domain is attached to*/
> +	struct list_head	devices;
> +	struct arm_smmu_device	*smmu;
> +};

Ah, if you have this struct you could just put

  u32 cache_tag; // ASID or VMID depending on domain type

And make both allocators local to the instance.

AFAIK the only specific thing that needs a global ASID is the SVA BTM
stuff and it already has code to handle collisions, it can just run
that code per-instance.

>  /* SMMU private data for each master */
>  struct arm_smmu_master {
>  	struct arm_smmu_device		*smmu;
>  	struct device			*dev;
>  	struct arm_smmu_domain		*domain;
> -	struct list_head		domain_head;
> +	struct list_head		list;

What is list for now?

Jason

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Michael Shavit <mshavit@google.com>
Cc: iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, will@kernel.org,
	nicolinc@nvidia.com, tina.zhang@intel.com,
	jean-philippe@linaro.org, robin.murphy@arm.com
Subject: Re: [RFC PATCH v1 1/8] iommu/arm-smmu-v3: Add list of installed_smmus
Date: Thu, 17 Aug 2023 16:05:55 -0300	[thread overview]
Message-ID: <ZN5vk9cVp0j0jd8T@nvidia.com> (raw)
In-Reply-To: <20230818021629.RFC.v1.1.I9df3dec9e33165276eba8e2dbf7025bfee286d90@changeid>

On Fri, Aug 18, 2023 at 02:16:23AM +0800, Michael Shavit wrote:
> diff --git a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
> index 83d2790b701e7..a9202d2045537 100644
> --- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
> +++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
> @@ -690,12 +690,20 @@ struct arm_smmu_stream {
>  	struct rb_node			node;
>  };
>  
> +/* List of smmu devices that a domain is installed to */
> +struct arm_smmu_installed_smmu {
> +	struct list_head	list;

'installed_smmus_item'

> +	/* List of masters that the domain is attached to*/
> +	struct list_head	devices;
> +	struct arm_smmu_device	*smmu;
> +};

Ah, if you have this struct you could just put

  u32 cache_tag; // ASID or VMID depending on domain type

And make both allocators local to the instance.

AFAIK the only specific thing that needs a global ASID is the SVA BTM
stuff and it already has code to handle collisions, it can just run
that code per-instance.

>  /* SMMU private data for each master */
>  struct arm_smmu_master {
>  	struct arm_smmu_device		*smmu;
>  	struct device			*dev;
>  	struct arm_smmu_domain		*domain;
> -	struct list_head		domain_head;
> +	struct list_head		list;

What is list for now?

Jason

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-08-17 19:05 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17 18:16 [RFC PATCH v1 0/8] Install domain onto multiple smmus Michael Shavit
2023-08-17 18:16 ` Michael Shavit
2023-08-17 18:16 ` [RFC PATCH v1 1/8] iommu/arm-smmu-v3: Add list of installed_smmus Michael Shavit
2023-08-17 18:16   ` Michael Shavit
2023-08-17 19:05   ` Jason Gunthorpe [this message]
2023-08-17 19:05     ` Jason Gunthorpe
2023-08-17 19:34   ` Robin Murphy
2023-08-17 19:34     ` Robin Murphy
2023-08-18  5:34     ` Michael Shavit
2023-08-18  5:34       ` Michael Shavit
2023-08-17 18:16 ` [RFC PATCH v1 2/8] iommu/arm-smmu-v3: Perform invalidations over installed_smmus Michael Shavit
2023-08-17 18:16   ` Michael Shavit
2023-08-17 19:20   ` Jason Gunthorpe
2023-08-17 19:20     ` Jason Gunthorpe
2023-08-17 19:41     ` Robin Murphy
2023-08-17 19:41       ` Robin Murphy
2023-08-18  3:44       ` Michael Shavit
2023-08-18  3:44         ` Michael Shavit
2023-08-18 13:51         ` Jason Gunthorpe
2023-08-18 13:51           ` Jason Gunthorpe
2023-08-21  8:33           ` Michael Shavit
2023-08-21  8:33             ` Michael Shavit
2023-08-21 11:57             ` Jason Gunthorpe
2023-08-21 11:57               ` Jason Gunthorpe
2023-08-22  8:17               ` Michael Shavit
2023-08-22  8:17                 ` Michael Shavit
2023-08-22  8:21                 ` Michael Shavit
2023-08-22  8:21                   ` Michael Shavit
2023-08-22 10:10                 ` Michael Shavit
2023-08-22 10:10                   ` Michael Shavit
2023-08-22 14:15                 ` Jason Gunthorpe
2023-08-22 14:15                   ` Jason Gunthorpe
2023-08-17 18:16 ` [RFC PATCH v1 3/8] iommu/arm-smmu-v3-sva: Allocate new ASID from installed_smmus Michael Shavit
2023-08-17 18:16   ` Michael Shavit
2023-08-17 18:38   ` Jason Gunthorpe
2023-08-17 18:38     ` Jason Gunthorpe
2023-08-21  9:31     ` Michael Shavit
2023-08-21  9:31       ` Michael Shavit
2023-08-21 11:54       ` Jason Gunthorpe
2023-08-21 11:54         ` Jason Gunthorpe
2023-08-21 13:38         ` Michael Shavit
2023-08-21 13:38           ` Michael Shavit
2023-08-21 13:50           ` Jason Gunthorpe
2023-08-21 13:50             ` Jason Gunthorpe
2023-08-21 14:16             ` Michael Shavit
2023-08-21 14:16               ` Michael Shavit
2023-08-21 14:26               ` Jason Gunthorpe
2023-08-21 14:26                 ` Jason Gunthorpe
2023-08-21 14:39                 ` Michael Shavit
2023-08-21 14:39                   ` Michael Shavit
2023-08-21 14:56                   ` Jason Gunthorpe
2023-08-21 14:56                     ` Jason Gunthorpe
2023-08-22  8:53                     ` Michael Shavit
2023-08-22  8:53                       ` Michael Shavit
2023-08-17 18:16 ` [RFC PATCH v1 4/8] iommu/arm-smmu-v3: check smmu compatibility on attach Michael Shavit
2023-08-17 18:16   ` Michael Shavit
2023-08-17 19:16   ` Robin Murphy
2023-08-17 19:16     ` Robin Murphy
2023-08-18  3:14     ` Michael Shavit
2023-08-18  3:14       ` Michael Shavit
2023-08-17 18:16 ` [RFC PATCH v1 5/8] iommu/arm-smmu-v3: Add arm_smmu_device as a parameter to domain_finalise Michael Shavit
2023-08-17 18:16   ` Michael Shavit
2023-08-17 18:16 ` [RFC PATCH v1 6/8] iommu/arm-smmu-v3: Free VMID when uninstalling domain from SMMU Michael Shavit
2023-08-17 18:16   ` Michael Shavit
2023-08-17 18:50   ` Jason Gunthorpe
2023-08-17 18:50     ` Jason Gunthorpe
2023-08-17 18:16 ` [RFC PATCH v1 7/8] iommu/arm-smmu-v3: check for domain initialization using pgtbl_ops Michael Shavit
2023-08-17 18:16   ` Michael Shavit
2023-08-17 18:16 ` [RFC PATCH v1 8/8] iommu/arm-smmu-v3: allow multi-SMMU domain installs Michael Shavit
2023-08-17 18:16   ` Michael Shavit

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=ZN5vk9cVp0j0jd8T@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=jean-philippe@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mshavit@google.com \
    --cc=nicolinc@nvidia.com \
    --cc=robin.murphy@arm.com \
    --cc=tina.zhang@intel.com \
    --cc=will@kernel.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 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.