All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Michael Shavit <mshavit@google.com>,
	iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Cc: baolu.lu@linux.intel.com, nicolinc@nvidia.com,
	tina.zhang@intel.com, jean-philippe@linaro.org, will@kernel.org,
	robin.murphy@arm.com, jgg@nvidia.com,
	Dawei Li <set_pte_at@outlook.com>, Jason Gunthorpe <jgg@ziepe.ca>,
	Joerg Roedel <joro@8bytes.org>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Mark Brown <broonie@kernel.org>
Subject: Re: [RFC PATCH v2 0/9] Install domain onto multiple smmus
Date: Wed, 23 Aug 2023 10:42:29 +0800	[thread overview]
Message-ID: <4ba43e04-965a-4002-ac8d-58a798c25975@linux.intel.com> (raw)
In-Reply-To: <20230822105738.1607365-1-mshavit@google.com>

On 2023/8/22 18:56, Michael Shavit wrote:
> 
> Hi all,
> 
> This series refactors the arm-smmu-v3 driver to support attaching
> domains onto masters belonging to different smmu devices.
> 
> The main objective of this series is allow further refactorings of
> arm-smmu-v3-sva. Specifically, we'd like to reach the state where:
> 1. A single SVA domain is allocated per MM/ASID

The core side of this work is under discussion.

https://lore.kernel.org/linux-iommu/20230808074944.7825-1-tina.zhang@intel.com/

Just FYI.

Best regards,
baolu

WARNING: multiple messages have this Message-ID (diff)
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Michael Shavit <mshavit@google.com>,
	iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Cc: baolu.lu@linux.intel.com, nicolinc@nvidia.com,
	tina.zhang@intel.com, jean-philippe@linaro.org, will@kernel.org,
	robin.murphy@arm.com, jgg@nvidia.com,
	Dawei Li <set_pte_at@outlook.com>, Jason Gunthorpe <jgg@ziepe.ca>,
	Joerg Roedel <joro@8bytes.org>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Mark Brown <broonie@kernel.org>
Subject: Re: [RFC PATCH v2 0/9] Install domain onto multiple smmus
Date: Wed, 23 Aug 2023 10:42:29 +0800	[thread overview]
Message-ID: <4ba43e04-965a-4002-ac8d-58a798c25975@linux.intel.com> (raw)
In-Reply-To: <20230822105738.1607365-1-mshavit@google.com>

On 2023/8/22 18:56, Michael Shavit wrote:
> 
> Hi all,
> 
> This series refactors the arm-smmu-v3 driver to support attaching
> domains onto masters belonging to different smmu devices.
> 
> The main objective of this series is allow further refactorings of
> arm-smmu-v3-sva. Specifically, we'd like to reach the state where:
> 1. A single SVA domain is allocated per MM/ASID

The core side of this work is under discussion.

https://lore.kernel.org/linux-iommu/20230808074944.7825-1-tina.zhang@intel.com/

Just FYI.

Best regards,
baolu

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

  parent reply	other threads:[~2023-08-23  2:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 10:56 [RFC PATCH v2 0/9] Install domain onto multiple smmus Michael Shavit
2023-08-22 10:56 ` Michael Shavit
2023-08-22 10:56 ` [RFC PATCH v2 1/9] iommu/arm-smmu-v3: group attached devices by smmu Michael Shavit
2023-08-22 10:56   ` Michael Shavit
2023-08-22 12:49   ` Jason Gunthorpe
2023-08-22 12:49     ` Jason Gunthorpe
2023-08-22 10:56 ` [RFC PATCH v2 2/9] iommu/arm-smmu-v3-sva: Move SVA optimization into arm_smmu_tlb_inv_range_asid Michael Shavit
2023-08-22 10:56   ` Michael Shavit
2023-08-22 10:56 ` [RFC PATCH v2 3/9] iommu/arm-smmu-v3: Issue invalidations commands to multiple SMMUs Michael Shavit
2023-08-22 10:56   ` Michael Shavit
2023-08-22 13:14   ` Jason Gunthorpe
2023-08-22 13:14     ` Jason Gunthorpe
2023-08-22 10:57 ` [RFC PATCH v2 4/9] iommu/arm-smmu-v3-sva: Allocate new ASID from installed_smmus Michael Shavit
2023-08-22 10:57   ` Michael Shavit
2023-08-22 13:19   ` Jason Gunthorpe
2023-08-22 13:19     ` Jason Gunthorpe
2023-08-23  7:26     ` Michael Shavit
2023-08-23  7:26       ` Michael Shavit
2023-08-22 10:57 ` [RFC PATCH v2 5/9] iommu/arm-smmu-v3: Alloc vmid from global pool Michael Shavit
2023-08-22 10:57   ` Michael Shavit
2023-08-22 10:57 ` [RFC PATCH v2 6/9] iommu/arm-smmu-v3: check smmu compatibility on attach Michael Shavit
2023-08-22 10:57   ` Michael Shavit
2023-08-22 10:57 ` [RFC PATCH v2 7/9] iommu/arm-smmu-v3: Add arm_smmu_device as a parameter to domain_finalise Michael Shavit
2023-08-22 10:57   ` Michael Shavit
2023-08-22 10:57 ` [RFC PATCH v2 8/9] iommu/arm-smmu-v3: check for domain initialization using pgtbl_ops Michael Shavit
2023-08-22 10:57   ` Michael Shavit
2023-08-22 10:57 ` [RFC PATCH v2 9/9] iommu/arm-smmu-v3: allow multi-SMMU domain installs Michael Shavit
2023-08-22 10:57   ` Michael Shavit
2023-08-23  2:42 ` Baolu Lu [this message]
2023-08-23  2:42   ` [RFC PATCH v2 0/9] Install domain onto multiple smmus Baolu Lu

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=4ba43e04-965a-4002-ac8d-58a798c25975@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=iommu@lists.linux.dev \
    --cc=jean-philippe@linaro.org \
    --cc=jgg@nvidia.com \
    --cc=jgg@ziepe.ca \
    --cc=joro@8bytes.org \
    --cc=kirill.shutemov@linux.intel.com \
    --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=set_pte_at@outlook.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.