From: robin.murphy@arm.com (Robin Murphy)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 3/4] ACPI: IORT: Skip SMMUv3 device ID map for two steps mappings
Date: Fri, 22 Sep 2017 14:21:57 +0100 [thread overview]
Message-ID: <d9f33a08-a1b8-002c-53d6-ce43b273c7df@arm.com> (raw)
In-Reply-To: <1505999838-52530-4-git-send-email-guohanjun@huawei.com>
On 21/09/17 14:17, Hanjun Guo wrote:
> From: Hanjun Guo <hanjun.guo@linaro.org>
>
> IORT revision C introduced SMMUv3 MSI support which adding a
> device ID mapping index in SMMUv3 sub table, to get the SMMUv3
> device ID mapping for the output ID (dev ID for ITS) and the
> link to which ITS.
>
> So if a platform supports SMMUv3 MSI for control interrupt,
> there will be a additional single map entry under SMMU, this
> will not introduce any difference for devices just use one
> step map to get its output ID and parent (ITS or SMMU), such
> as PCI/NC/PMCG ---> ITS or PCI/NC ---> SMMU, but we need to
> do the special handling for two steps map case such as
> PCI/NC--->SMMUv3--->ITS.
>
> Take a PCI hostbridge for example,
>
> |----------------------|
> | Root Complex Node |
> |----------------------|
> | map entry[x] |
> |----------------------|
> | id value |
> | output_reference |
> |---|------------------|
> |
> | |----------------------|
> |-->| SMMUv3 |
> |----------------------|
> | SMMU dev ID |
> | mapping index 0 |
> |----------------------|
> | map entry[0] |
> |----------------------|
> | id value |
> | output_reference-----------> ITS 1 (SMMU MSI domain)
> |----------------------|
> | map entry[1] |
> |----------------------|
> | id value |
> | output_reference-----------> ITS 2 (PCI MSI domain)
> |----------------------|
>
> When the SMMU dev ID mapping index is 0, there is entry[0]
> to map to a ITS, we need to skip that map entry for PCI
> or NC (named component), or we may get the wrong ITS parent.
>
> For now we have two APIs for ID mapping, iort_node_map_id()
> and iort_node_map_platform_id(), and iort_node_map_id() is
> used for optional two steps mapping, so we just need to
> skip the map entry in iort_node_map_id() for non-SMMUv3
> devices.
>
> Signed-off-by: Hanjun Guo <hanjun.guo@linaro.org>
> ---
> drivers/acpi/arm64/iort.c | 43 ++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 42 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c
> index db71d7f..269959e 100644
> --- a/drivers/acpi/arm64/iort.c
> +++ b/drivers/acpi/arm64/iort.c
> @@ -366,6 +366,34 @@ struct acpi_iort_node *iort_node_get_id(struct acpi_iort_node *node,
> return NULL;
> }
>
> +static int iort_get_smmu_v3_id_mapping_index(struct acpi_iort_node *node,
> + u32 *index)
> +{
> + struct acpi_iort_smmu_v3 *smmu;
> +
> + /*
> + * SMMUv3 dev ID mapping index was introdueced in revision 1
> + * table, not avaible in revision 0
> + */
> + if (node->revision < 1)
> + return -EINVAL;
> +
> + smmu = (struct acpi_iort_smmu_v3 *)node->node_data;
> + /* if any of the gsi for control interrupts is not 0, ignore the MSI */
> + if (smmu->event_gsiv || smmu->pri_gsiv || smmu->gerr_gsiv
> + || smmu->sync_gsiv)
To repeat my previous comments, the ID mapping index is only ignored if
*all* interrupts are GSIV-based.
It would be quite reasonable for gerr to be wired while everything else
uses MSIs, especially since that's effectively the only reliable way to
get MSI aborts reported if things are completely hosed.
> + return -EINVAL;
> +
> + if (smmu->id_mapping_index >= node->mapping_count) {
> + pr_err(FW_BUG "[node %p type %d] ID mapping index overflows valid mappings\n",
> + node, node->type);
> + return -EINVAL;
> + }
> +
> + *index = smmu->id_mapping_index;
> + return 0;
> +}
> +
> static struct acpi_iort_node *iort_node_map_id(struct acpi_iort_node *node,
> u32 id_in, u32 *id_out,
> u8 type_mask)
> @@ -375,7 +403,9 @@ static struct acpi_iort_node *iort_node_map_id(struct acpi_iort_node *node,
> /* Parse the ID mapping tree to find specified node type */
> while (node) {
> struct acpi_iort_id_mapping *map;
> - int i;
> + int i, ret = -EINVAL;
> + /* big enough for an invalid id index in practical */
> + u32 index = U32_MAX;
And again, more of a style nit, but indices must be sufficiently small
to fit into the positive half of an int, so *_id_mapping_index() really
doesn't need this complication of passing a separate output argument.
Robin.
> if (IORT_TYPE_MASK(node->type) & type_mask) {
> if (id_out)
> @@ -396,8 +426,19 @@ static struct acpi_iort_node *iort_node_map_id(struct acpi_iort_node *node,
> goto fail_map;
> }
>
> + /*
> + * we need to get SMMUv3 dev ID mapping index and skip its
> + * associated ID map for single mapping cases.
> + */
> + if (node->type == ACPI_IORT_NODE_SMMU_V3)
> + ret = iort_get_smmu_v3_id_mapping_index(node, &index);
> +
> /* Do the ID translation */
> for (i = 0; i < node->mapping_count; i++, map++) {
> + /* if it's a SMMUv3 device id mapping index, skip it */
> + if (!ret && i == index)
> + continue;
> +
> if (!iort_id_map(map, node->type, id, &id))
> break;
> }
>
next prev parent reply other threads:[~2017-09-22 13:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 13:17 [RFC PATCH v2 0/4] IORT SMMUv3 MSI support Hanjun Guo
2017-09-21 13:17 ` [RFC PATCH v2 1/4] ACPICA: Add SMMUv3 device ID mapping index support Hanjun Guo
2017-09-22 11:25 ` Lorenzo Pieralisi
2017-09-21 13:17 ` [RFC PATCH v2 2/4] ACPI: IORT: lookup iort node via fwnode Hanjun Guo
2017-09-21 13:17 ` [RFC PATCH v2 3/4] ACPI: IORT: Skip SMMUv3 device ID map for two steps mappings Hanjun Guo
2017-09-22 12:53 ` Lorenzo Pieralisi
2017-09-26 21:39 ` Hanjun Guo
2017-09-22 13:21 ` Robin Murphy [this message]
2017-09-26 19:04 ` Hanjun Guo
2017-09-21 13:17 ` [RFC PATCH v2 4/4] ACPI: IORT: SMMUv3 nodes MSI support Hanjun Guo
2017-09-22 13:07 ` Lorenzo Pieralisi
2017-09-27 0:34 ` Hanjun Guo
2017-09-22 11:22 ` [RFC PATCH v2 0/4] IORT SMMUv3 " Lorenzo Pieralisi
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=d9f33a08-a1b8-002c-53d6-ce43b273c7df@arm.com \
--to=robin.murphy@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).