From: Nicolin Chen <nicolinc@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>,
<robin.murphy@arm.com>, <jean-philippe@linaro.org>,
<jgg@nvidia.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Joerg Roedel <joro@8bytes.org>, Kevin Tian <kevin.tian@intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Lu Baolu <baolu.lu@linux.intel.com>,
Mark Brown <broonie@kernel.org>,
Yicong Yang <yangyicong@hisilicon.com>
Subject: Re: [PATCH v7 6/9] iommu/arm-smmu-v3: Move CD table to arm_smmu_master
Date: Thu, 31 Aug 2023 15:32:46 -0700 [thread overview]
Message-ID: <ZPEVDnlGOf7s0NoK@Asurada-Nvidia> (raw)
In-Reply-To: <20230901014413.v7.6.Ice063dcf87d1b777a72e008d9e3406d2bcf6d876@changeid>
On Fri, Sep 01, 2023 at 01:44:35AM +0800, Michael Shavit wrote:
> With this change, each master will now own its own CD table instead of
> sharing one with other masters attached to the same domain. Attaching a
> stage 1 domain installs CD entries into the master's CD table. SVA
> writes its CD entries into each master's CD table if the domain is
> shared across masters.
>
> Also add the device to the devices list before writing the CD to the
> table so that SVA will know that the CD needs to be re-written to this
> device's CD table as well if it decides to update the CD's ASID
> concurrently with this function.
>
> Tested-by: Nicolin Chen <nicolinc@nvidia.com>
> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
> Signed-off-by: Michael Shavit <mshavit@google.com>
Reviewed-by: Nicolin Chen <nicolinc@nvidia.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-31 22:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 17:44 [PATCH v7 0/9] Refactor the SMMU's CD table ownership Michael Shavit
2023-08-31 17:44 ` [PATCH v7 1/9] iommu/arm-smmu-v3: Move ctx_desc out of s1_cfg Michael Shavit
2023-08-31 17:44 ` [PATCH v7 2/9] iommu/arm-smmu-v3: Replace s1_cfg with cdtab_cfg Michael Shavit
2023-08-31 17:44 ` [PATCH v7 3/9] iommu/arm-smmu-v3: Encapsulate ctx_desc_cfg init in alloc_cd_tables Michael Shavit
2023-08-31 17:44 ` [PATCH v7 4/9] iommu/arm-smmu-v3: move stall_enabled to the cd table Michael Shavit
2023-08-31 17:44 ` [PATCH v7 5/9] iommu/arm-smmu-v3: Refactor write_ctx_desc Michael Shavit
2023-08-31 17:44 ` [PATCH v7 6/9] iommu/arm-smmu-v3: Move CD table to arm_smmu_master Michael Shavit
2023-08-31 22:32 ` Nicolin Chen [this message]
2023-08-31 17:44 ` [PATCH v7 7/9] iommu/arm-smmu-v3: Cleanup arm_smmu_domain_finalise Michael Shavit
2023-08-31 17:44 ` [PATCH v7 8/9] iommu/arm-smmu-v3: Update comment about STE liveness Michael Shavit
2023-08-31 17:44 ` [PATCH v7 9/9] iommu/arm-smmu-v3: Rename cdcfg to cd_table Michael Shavit
2023-09-01 0:00 ` [PATCH v7 0/9] Refactor the SMMU's CD table ownership Nicolin Chen
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=ZPEVDnlGOf7s0NoK@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=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=kevin.tian@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mshavit@google.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.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