From: Nicolin Chen <nicolinc@nvidia.com>
To: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Cc: <iommu@lists.linux.dev>, <linux-arm-kernel@lists.infradead.org>,
<robin.murphy@arm.com>, <will@kernel.org>, <joro@8bytes.org>,
<jgg@nvidia.com>, <ryan.roberts@arm.com>, <mark.rutland@arm.com>,
<kevin.tian@intel.com>, <mshavit@google.com>,
<eric.auger@redhat.com>, <joao.m.martins@oracle.com>,
<jiangkunkun@huawei.com>, <zhukeqian1@huawei.com>,
<linuxarm@huawei.com>
Subject: Re: [PATCH v6 3/6] iommu/arm-smmu-v3: Add feature detection for HTTU
Date: Thu, 13 Jun 2024 10:50:16 -0700 [thread overview]
Message-ID: <ZmsxWOmR13KyLc9S@Asurada-Nvidia> (raw)
In-Reply-To: <20240613144149.38672-4-shameerali.kolothum.thodi@huawei.com>
On Thu, Jun 13, 2024 at 03:41:46PM +0100, Shameer Kolothum wrote:
> From: Jean-Philippe Brucker <jean-philippe@linaro.org>
>
> If the SMMU supports it and the kernel was built with HTTU support,
> Probe support for Hardware Translation Table Update (HTTU) which is
> essentially to enable hardware update of access and dirty flags.
>
> Probe and set the smmu::features for Hardware Dirty and Hardware Access
> bits. This is in preparation, to enable it on the context descriptors of
> stage 1 format.
>
> Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
> Reviewed-by: Ryan Roberts <ryan.roberts@arm.com>
> Reviewed-by: Kevin Tian <kevin.tian@intel.com>
> Signed-off-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Reviewed-by: Nicolin Chen <nicolinc@nvidia.com>
> +static void arm_smmu_get_httu(struct arm_smmu_device *smmu, u32 reg)
> +{
> + u32 fw_features = smmu->features & (ARM_SMMU_FEAT_HA | ARM_SMMU_FEAT_HD);
> + u32 httu = FIELD_GET(IDR0_HTTU, reg);
> + u32 hw_features = 0;
> +
> + switch (httu) {
It seems that we can drop the httu variable too. But it's quite
unimportant, so let's have it as-is if there is no other reason
to respin the series.
next prev parent reply other threads:[~2024-06-13 17:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 14:41 [PATCH v6 0/6] Add IOMMUFD dirty tracking support for SMMUv3 Shameer Kolothum
2024-06-13 14:41 ` [PATCH v6 1/6] iommu/arm-smmu-v3: Factor out a common domain alloc Shameer Kolothum
2024-06-13 14:41 ` [PATCH v6 2/6] iommu/arm-smmu-v3: Add support for domain_alloc_user fn Shameer Kolothum
2024-06-13 14:41 ` [PATCH v6 3/6] iommu/arm-smmu-v3: Add feature detection for HTTU Shameer Kolothum
2024-06-13 17:50 ` Nicolin Chen [this message]
2024-06-13 14:41 ` [PATCH v6 4/6] iommu/io-pgtable-arm: Add read_and_clear_dirty() support Shameer Kolothum
2024-06-13 14:41 ` [PATCH v6 5/6] iommu/arm-smmu-v3: Add support for dirty tracking in domain alloc Shameer Kolothum
2024-06-13 14:41 ` [PATCH v6 6/6] iommu/arm-smmu-v3: Enable HTTU for stage1 with io-pgtable mapping Shameer Kolothum
2024-07-02 13:15 ` [PATCH v6 0/6] Add IOMMUFD dirty tracking support for SMMUv3 Shameerali Kolothum Thodi
2024-07-02 13:19 ` Will Deacon
2024-07-02 13:25 ` Shameerali Kolothum Thodi
2024-07-02 18:45 ` Will Deacon
2024-07-03 10:20 ` Shameerali Kolothum Thodi
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=ZmsxWOmR13KyLc9S@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jiangkunkun@huawei.com \
--cc=joao.m.martins@oracle.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mshavit@google.com \
--cc=robin.murphy@arm.com \
--cc=ryan.roberts@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=will@kernel.org \
--cc=zhukeqian1@huawei.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