From: Jason Gunthorpe <jgg@nvidia.com>
To: Nicolin Chen <nicolinc@nvidia.com>
Cc: will@kernel.org, robin.murphy@arm.com, joro@8bytes.org,
thierry.reding@gmail.com, vdumpa@nvidia.com,
jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v11 7/9] iommu/arm-smmu-v3: Add struct arm_smmu_impl
Date: Wed, 14 Aug 2024 18:52:46 -0300 [thread overview]
Message-ID: <20240814215246.GX2032816@nvidia.com> (raw)
In-Reply-To: <8f6fd78b4c4358e65e9d171d90aa4a3dac392f09.1722993435.git.nicolinc@nvidia.com>
On Tue, Aug 06, 2024 at 07:11:52PM -0700, Nicolin Chen wrote:
>
> -static int arm_smmu_device_acpi_probe(struct platform_device *pdev,
> - struct arm_smmu_device *smmu)
> +static struct arm_smmu_device *
> +arm_smmu_impl_acpi_probe(struct arm_smmu_device *smmu,
> + struct acpi_iort_node *node)
> +{
> + /*
> + * DSDT might hold some SMMU extension, so we have no option but to go
> + * through the ACPI tables unconditionally. On success, this returns a
> + * copy of smmu struct holding an impl pointer. Otherwise, an impl may
> + * choose to return an ERR_PTR as an error out, or to return the pass-
> + * in smmu pointer as a fallback to the standard SMMU.
> + */
> + return arm_smmu_impl_acpi_dsdt_probe(smmu, node);
> +}
Lets generalize this a bit more and have the impl mechanism work for
DT too.. Keep the main probe the same and add a new function after the
dt/acpi steps:
smmu = arm_smmu_probe_impl(smmu);
if (IS_ERR(smmu))
return PTR_ERR(smmu);
Which is more like:
/*
* Probe all the compiled in implementations. Each one checks to see if it
* matches this HW and if so returns a devm_krealloc'd arm_smmu_device which
* replaces the callers. Otherwise the original is returned or ERR_PTR.
*
*/
static struct arm_smmu_device *arm_smmu_probe_impl(struct arm_smmu_device *orig_smmu)
{
struct arm_smmu_device *new_smmu;
int ret;
new_smmu = tegra241_cmdqv_acpi_dsdt_probe(orig_smmu);
if (new_smmu != ERR_PTR(-ENODEV))
goto out_new_impl;
return orig_smmu;
out_new_impl:
if (IS_ERR(new_smmu))
return new_smmu;
/* FIXME: check is this ordering OK during remove? */
ret = devm_add_action_or_reset(new_smmu->dev, arm_smmu_impl_remove,
new_smmu);
if (ret)
return ERR_PTR(ret);
return new_smmu;
}
Easy to add new sub implementations. Provide an inline ENODEV sub in
the header file for tegra241_cmdqv_acpi_dsdt_probe
Add something like this to the header to get the ACPI node:
static inline struct acpi_iort_node *
arm_smmu_get_iort_node(struct arm_smmu_device *smmu)
{
return *(struct acpi_iort_node **)dev_get_platdata(smmu->dev);
}
Since it isn't passed down
> @@ -4560,6 +4602,7 @@ static void arm_smmu_device_remove(struct platform_device *pdev)
> {
> struct arm_smmu_device *smmu = platform_get_drvdata(pdev);
>
> + arm_smmu_impl_remove(smmu);
Can't call this if devm has been used to set it up, and this would be
in the wrong order anyhow. Just remove it.. I guess the devm was put
for this to avoid adding goto error unwind to probe?
> +struct arm_smmu_impl {
> + int (*device_reset)(struct arm_smmu_device *smmu);
> + void (*device_remove)(struct arm_smmu_device *smmu);
> + struct arm_smmu_cmdq *(*get_secondary_cmdq)(struct arm_smmu_device *smmu);
> +};
Can we put the word "ops" into this struct somehow? That would be a
more typically kernely name.
arm_smmu_impl_ops perhaps?
> struct arm_smmu_device {
> struct device *dev;
> + /* An SMMUv3 implementation */
The comment is self explanatory
Jason
next prev parent reply other threads:[~2024-08-14 21:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 2:11 [PATCH v11 0/9] Add Tegra241 (Grace) CMDQV Support (part 1/2) Nicolin Chen
2024-08-07 2:11 ` [PATCH v11 1/9] iommu/arm-smmu-v3: Issue a batch of commands to the same cmdq Nicolin Chen
2024-08-07 2:11 ` [PATCH v11 2/9] iommu/arm-smmu-v3: Enforce arm_smmu_cmdq_build_sync_cmd Nicolin Chen
2024-08-16 13:53 ` Will Deacon
2024-08-16 17:56 ` Nicolin Chen
2024-08-07 2:11 ` [PATCH v11 3/9] iommu/arm-smmu-v3: Pass in cmdq pointer to arm_smmu_cmdq_build_sync_cmd Nicolin Chen
2024-08-14 17:26 ` Jason Gunthorpe
2024-08-07 2:11 ` [PATCH v11 4/9] iommu/arm-smmu-v3: Pass in cmdq pointer to arm_smmu_cmdq_init Nicolin Chen
2024-08-14 17:27 ` Jason Gunthorpe
2024-08-07 2:11 ` [PATCH v11 5/9] iommu/arm-smmu-v3: Make symbols public for CONFIG_TEGRA241_CMDQV Nicolin Chen
2024-08-07 2:11 ` [PATCH v11 6/9] iommu/arm-smmu-v3: Add ARM_SMMU_OPT_SECONDARY_CMDQ_CS_NONE_ONLY Nicolin Chen
2024-08-14 17:31 ` Jason Gunthorpe
2024-08-07 2:11 ` [PATCH v11 7/9] iommu/arm-smmu-v3: Add struct arm_smmu_impl Nicolin Chen
2024-08-14 21:52 ` Jason Gunthorpe [this message]
2024-08-15 5:26 ` Nicolin Chen
2024-08-07 2:11 ` [PATCH v11 8/9] iommu/arm-smmu-v3: Add in-kernel support for NVIDIA Tegra241 (Grace) CMDQV Nicolin Chen
2024-08-14 21:57 ` Jason Gunthorpe
2024-08-15 5:27 ` Nicolin Chen
2024-08-16 14:19 ` Will Deacon
2024-08-16 17:41 ` Nicolin Chen
2024-08-23 15:38 ` Will Deacon
2024-08-24 0:11 ` Nicolin Chen
2024-08-07 2:11 ` [PATCH v11 9/9] iommu/tegra241-cmdqv: Limit CMDs for guest owned VINTF Nicolin Chen
2024-08-16 13:21 ` Will Deacon
2024-08-16 17:34 ` Nicolin Chen
2024-08-16 18:15 ` Nicolin Chen
2024-08-16 19:42 ` Nicolin Chen
2024-08-19 17:39 ` 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=20240814215246.GX2032816@nvidia.com \
--to=jgg@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jonathanh@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=thierry.reding@gmail.com \
--cc=vdumpa@nvidia.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.