From: Robert Richter <robert.richter-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
To: Will.Deacon-5wv7dgnIgG8@public.gmane.org,
lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org
Cc: gklkml16-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
sudeep.holla-5wv7dgnIgG8@public.gmane.org,
rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
jnair-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org,
linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Ganapatrao Kulkarni
<ganapatrao.kulkarni-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>,
lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
lv.zheng-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH v4] acpi/iort: numa: Add numa node mapping for smmuv3 devices
Date: Tue, 15 Aug 2017 17:02:13 +0200 [thread overview]
Message-ID: <20170815150213.GD18024@rric.localdomain> (raw)
In-Reply-To: <20170725050237.11033-1-ganapatrao.kulkarni-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
Lorenzo, Will,
On 25.07.17 10:32:37, Ganapatrao Kulkarni wrote:
> ARM IORT specification(rev. C) has added provision to define proximity
> domain in SMMUv3 IORT table. Adding required code to parse Proximity
> domain and set numa_node of smmv3 platform devices.
>
> Add code to parse proximity domain in SMMUv3 IORT table to
> set numa node mapping for smmuv3 devices.
>
> Signed-off-by: Ganapatrao Kulkarni <ganapatrao.kulkarni-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
> ---
>
> This patch has dependency on header file patch [1], which is
> already merged to linux-pm.
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=c944230064eb65e4fa018d86779b4fd200b1d7e7
>
> v4:
> - Fix compilation issue in !CONFIG_NUMA
>
> v3:
> - Addressed Lorenzo Pieralisi comment.
>
> v2:
> - Changed as per Lorenzo Pieralisi and Hanjun Guo suggestions.
>
> v1:
> - Initial patch
>
> drivers/acpi/arm64/iort.c | 33 +++++++++++++++++++++++++++++++--
> 1 file changed, 31 insertions(+), 2 deletions(-)
could this patch being scheduled for v4.14?
Thanks,
-Robert
>
> diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c
> index a3215ee..c5c82c3 100644
> --- a/drivers/acpi/arm64/iort.c
> +++ b/drivers/acpi/arm64/iort.c
> @@ -908,6 +908,28 @@ static bool __init arm_smmu_v3_is_coherent(struct acpi_iort_node *node)
> return smmu->flags & ACPI_IORT_SMMU_V3_COHACC_OVERRIDE;
> }
>
> +#if defined(CONFIG_ACPI_NUMA) && (ACPI_CA_VERSION >= 0x20170629)
> +/*
> + * set numa proximity domain for smmuv3 device
> + */
> +static void __init arm_smmu_v3_set_proximity(struct acpi_iort_node *node,
> + struct device *dev)
> +{
> + struct acpi_iort_smmu_v3 *smmu;
> +
> + smmu = (struct acpi_iort_smmu_v3 *)node->node_data;
> + if (smmu->flags & ACPI_IORT_SMMU_V3_PXM_VALID) {
> + set_dev_node(dev, acpi_map_pxm_to_node(smmu->pxm));
> + pr_info("SMMUV3[%llx] Mapped to Proximity domain %d\n",
> + smmu->base_address,
> + smmu->pxm);
> + }
> +}
> +#else
> +static void __init arm_smmu_v3_set_proximity(struct acpi_iort_node *node,
> + struct device *dev) { }
> +#endif
> +
> static int __init arm_smmu_count_resources(struct acpi_iort_node *node)
> {
> struct acpi_iort_smmu *smmu;
> @@ -977,20 +999,24 @@ struct iort_iommu_config {
> int (*iommu_count_resources)(struct acpi_iort_node *node);
> void (*iommu_init_resources)(struct resource *res,
> struct acpi_iort_node *node);
> + void (*iommu_set_proximity)(struct acpi_iort_node *node,
> + struct device *dev);
> };
>
> static const struct iort_iommu_config iort_arm_smmu_v3_cfg __initconst = {
> .name = "arm-smmu-v3",
> .iommu_is_coherent = arm_smmu_v3_is_coherent,
> .iommu_count_resources = arm_smmu_v3_count_resources,
> - .iommu_init_resources = arm_smmu_v3_init_resources
> + .iommu_init_resources = arm_smmu_v3_init_resources,
> + .iommu_set_proximity = arm_smmu_v3_set_proximity
> };
>
> static const struct iort_iommu_config iort_arm_smmu_cfg __initconst = {
> .name = "arm-smmu",
> .iommu_is_coherent = arm_smmu_is_coherent,
> .iommu_count_resources = arm_smmu_count_resources,
> - .iommu_init_resources = arm_smmu_init_resources
> + .iommu_init_resources = arm_smmu_init_resources,
> + .iommu_set_proximity = NULL
> };
>
> static __init
> @@ -1028,6 +1054,9 @@ static int __init iort_add_smmu_platform_device(struct acpi_iort_node *node)
> if (!pdev)
> return -ENOMEM;
>
> + if (ops->iommu_set_proximity)
> + ops->iommu_set_proximity(node, &pdev->dev);
> +
> count = ops->iommu_count_resources(node);
>
> r = kcalloc(count, sizeof(*r), GFP_KERNEL);
> --
> 2.9.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: robert.richter@cavium.com (Robert Richter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] acpi/iort: numa: Add numa node mapping for smmuv3 devices
Date: Tue, 15 Aug 2017 17:02:13 +0200 [thread overview]
Message-ID: <20170815150213.GD18024@rric.localdomain> (raw)
In-Reply-To: <20170725050237.11033-1-ganapatrao.kulkarni@cavium.com>
Lorenzo, Will,
On 25.07.17 10:32:37, Ganapatrao Kulkarni wrote:
> ARM IORT specification(rev. C) has added provision to define proximity
> domain in SMMUv3 IORT table. Adding required code to parse Proximity
> domain and set numa_node of smmv3 platform devices.
>
> Add code to parse proximity domain in SMMUv3 IORT table to
> set numa node mapping for smmuv3 devices.
>
> Signed-off-by: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>
> ---
>
> This patch has dependency on header file patch [1], which is
> already merged to linux-pm.
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=c944230064eb65e4fa018d86779b4fd200b1d7e7
>
> v4:
> - Fix compilation issue in !CONFIG_NUMA
>
> v3:
> - Addressed Lorenzo Pieralisi comment.
>
> v2:
> - Changed as per Lorenzo Pieralisi and Hanjun Guo suggestions.
>
> v1:
> - Initial patch
>
> drivers/acpi/arm64/iort.c | 33 +++++++++++++++++++++++++++++++--
> 1 file changed, 31 insertions(+), 2 deletions(-)
could this patch being scheduled for v4.14?
Thanks,
-Robert
>
> diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c
> index a3215ee..c5c82c3 100644
> --- a/drivers/acpi/arm64/iort.c
> +++ b/drivers/acpi/arm64/iort.c
> @@ -908,6 +908,28 @@ static bool __init arm_smmu_v3_is_coherent(struct acpi_iort_node *node)
> return smmu->flags & ACPI_IORT_SMMU_V3_COHACC_OVERRIDE;
> }
>
> +#if defined(CONFIG_ACPI_NUMA) && (ACPI_CA_VERSION >= 0x20170629)
> +/*
> + * set numa proximity domain for smmuv3 device
> + */
> +static void __init arm_smmu_v3_set_proximity(struct acpi_iort_node *node,
> + struct device *dev)
> +{
> + struct acpi_iort_smmu_v3 *smmu;
> +
> + smmu = (struct acpi_iort_smmu_v3 *)node->node_data;
> + if (smmu->flags & ACPI_IORT_SMMU_V3_PXM_VALID) {
> + set_dev_node(dev, acpi_map_pxm_to_node(smmu->pxm));
> + pr_info("SMMUV3[%llx] Mapped to Proximity domain %d\n",
> + smmu->base_address,
> + smmu->pxm);
> + }
> +}
> +#else
> +static void __init arm_smmu_v3_set_proximity(struct acpi_iort_node *node,
> + struct device *dev) { }
> +#endif
> +
> static int __init arm_smmu_count_resources(struct acpi_iort_node *node)
> {
> struct acpi_iort_smmu *smmu;
> @@ -977,20 +999,24 @@ struct iort_iommu_config {
> int (*iommu_count_resources)(struct acpi_iort_node *node);
> void (*iommu_init_resources)(struct resource *res,
> struct acpi_iort_node *node);
> + void (*iommu_set_proximity)(struct acpi_iort_node *node,
> + struct device *dev);
> };
>
> static const struct iort_iommu_config iort_arm_smmu_v3_cfg __initconst = {
> .name = "arm-smmu-v3",
> .iommu_is_coherent = arm_smmu_v3_is_coherent,
> .iommu_count_resources = arm_smmu_v3_count_resources,
> - .iommu_init_resources = arm_smmu_v3_init_resources
> + .iommu_init_resources = arm_smmu_v3_init_resources,
> + .iommu_set_proximity = arm_smmu_v3_set_proximity
> };
>
> static const struct iort_iommu_config iort_arm_smmu_cfg __initconst = {
> .name = "arm-smmu",
> .iommu_is_coherent = arm_smmu_is_coherent,
> .iommu_count_resources = arm_smmu_count_resources,
> - .iommu_init_resources = arm_smmu_init_resources
> + .iommu_init_resources = arm_smmu_init_resources,
> + .iommu_set_proximity = NULL
> };
>
> static __init
> @@ -1028,6 +1054,9 @@ static int __init iort_add_smmu_platform_device(struct acpi_iort_node *node)
> if (!pdev)
> return -ENOMEM;
>
> + if (ops->iommu_set_proximity)
> + ops->iommu_set_proximity(node, &pdev->dev);
> +
> count = ops->iommu_count_resources(node);
>
> r = kcalloc(count, sizeof(*r), GFP_KERNEL);
> --
> 2.9.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Robert Richter <robert.richter@cavium.com>
To: Will.Deacon@arm.com, lorenzo.pieralisi@arm.com
Cc: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org,
iommu@lists.linux-foundation.org, hanjun.guo@linaro.org,
sudeep.holla@arm.com, robin.murphy@arm.com, lv.zheng@intel.com,
joro@8bytes.org, rjw@rjwysocki.net, lenb@kernel.org,
jnair@caviumnetworks.com, gklkml16@gmail.com
Subject: Re: [PATCH v4] acpi/iort: numa: Add numa node mapping for smmuv3 devices
Date: Tue, 15 Aug 2017 17:02:13 +0200 [thread overview]
Message-ID: <20170815150213.GD18024@rric.localdomain> (raw)
In-Reply-To: <20170725050237.11033-1-ganapatrao.kulkarni@cavium.com>
Lorenzo, Will,
On 25.07.17 10:32:37, Ganapatrao Kulkarni wrote:
> ARM IORT specification(rev. C) has added provision to define proximity
> domain in SMMUv3 IORT table. Adding required code to parse Proximity
> domain and set numa_node of smmv3 platform devices.
>
> Add code to parse proximity domain in SMMUv3 IORT table to
> set numa node mapping for smmuv3 devices.
>
> Signed-off-by: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>
> ---
>
> This patch has dependency on header file patch [1], which is
> already merged to linux-pm.
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=c944230064eb65e4fa018d86779b4fd200b1d7e7
>
> v4:
> - Fix compilation issue in !CONFIG_NUMA
>
> v3:
> - Addressed Lorenzo Pieralisi comment.
>
> v2:
> - Changed as per Lorenzo Pieralisi and Hanjun Guo suggestions.
>
> v1:
> - Initial patch
>
> drivers/acpi/arm64/iort.c | 33 +++++++++++++++++++++++++++++++--
> 1 file changed, 31 insertions(+), 2 deletions(-)
could this patch being scheduled for v4.14?
Thanks,
-Robert
>
> diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c
> index a3215ee..c5c82c3 100644
> --- a/drivers/acpi/arm64/iort.c
> +++ b/drivers/acpi/arm64/iort.c
> @@ -908,6 +908,28 @@ static bool __init arm_smmu_v3_is_coherent(struct acpi_iort_node *node)
> return smmu->flags & ACPI_IORT_SMMU_V3_COHACC_OVERRIDE;
> }
>
> +#if defined(CONFIG_ACPI_NUMA) && (ACPI_CA_VERSION >= 0x20170629)
> +/*
> + * set numa proximity domain for smmuv3 device
> + */
> +static void __init arm_smmu_v3_set_proximity(struct acpi_iort_node *node,
> + struct device *dev)
> +{
> + struct acpi_iort_smmu_v3 *smmu;
> +
> + smmu = (struct acpi_iort_smmu_v3 *)node->node_data;
> + if (smmu->flags & ACPI_IORT_SMMU_V3_PXM_VALID) {
> + set_dev_node(dev, acpi_map_pxm_to_node(smmu->pxm));
> + pr_info("SMMUV3[%llx] Mapped to Proximity domain %d\n",
> + smmu->base_address,
> + smmu->pxm);
> + }
> +}
> +#else
> +static void __init arm_smmu_v3_set_proximity(struct acpi_iort_node *node,
> + struct device *dev) { }
> +#endif
> +
> static int __init arm_smmu_count_resources(struct acpi_iort_node *node)
> {
> struct acpi_iort_smmu *smmu;
> @@ -977,20 +999,24 @@ struct iort_iommu_config {
> int (*iommu_count_resources)(struct acpi_iort_node *node);
> void (*iommu_init_resources)(struct resource *res,
> struct acpi_iort_node *node);
> + void (*iommu_set_proximity)(struct acpi_iort_node *node,
> + struct device *dev);
> };
>
> static const struct iort_iommu_config iort_arm_smmu_v3_cfg __initconst = {
> .name = "arm-smmu-v3",
> .iommu_is_coherent = arm_smmu_v3_is_coherent,
> .iommu_count_resources = arm_smmu_v3_count_resources,
> - .iommu_init_resources = arm_smmu_v3_init_resources
> + .iommu_init_resources = arm_smmu_v3_init_resources,
> + .iommu_set_proximity = arm_smmu_v3_set_proximity
> };
>
> static const struct iort_iommu_config iort_arm_smmu_cfg __initconst = {
> .name = "arm-smmu",
> .iommu_is_coherent = arm_smmu_is_coherent,
> .iommu_count_resources = arm_smmu_count_resources,
> - .iommu_init_resources = arm_smmu_init_resources
> + .iommu_init_resources = arm_smmu_init_resources,
> + .iommu_set_proximity = NULL
> };
>
> static __init
> @@ -1028,6 +1054,9 @@ static int __init iort_add_smmu_platform_device(struct acpi_iort_node *node)
> if (!pdev)
> return -ENOMEM;
>
> + if (ops->iommu_set_proximity)
> + ops->iommu_set_proximity(node, &pdev->dev);
> +
> count = ops->iommu_count_resources(node);
>
> r = kcalloc(count, sizeof(*r), GFP_KERNEL);
> --
> 2.9.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-08-15 15:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 5:02 [PATCH v4] acpi/iort: numa: Add numa node mapping for smmuv3 devices Ganapatrao Kulkarni
2017-07-25 5:02 ` Ganapatrao Kulkarni
2017-07-25 5:02 ` Ganapatrao Kulkarni
2017-07-25 15:13 ` Robert Richter
2017-07-25 15:13 ` Robert Richter
2017-07-25 16:01 ` Lorenzo Pieralisi
2017-07-25 16:01 ` Lorenzo Pieralisi
[not found] ` <20170725151305.GU17961-vWBEXY7mpu582hYKe6nXyg@public.gmane.org>
2017-08-02 16:21 ` Lorenzo Pieralisi
2017-08-02 16:21 ` Lorenzo Pieralisi
2017-08-02 16:21 ` Lorenzo Pieralisi
2017-08-03 13:35 ` Hanjun Guo
2017-08-03 13:35 ` Hanjun Guo
2017-08-03 13:35 ` Hanjun Guo
2017-08-03 13:40 ` Hanjun Guo
2017-08-03 13:40 ` Hanjun Guo
2017-08-03 13:40 ` Hanjun Guo
2017-08-03 13:52 ` Lorenzo Pieralisi
2017-08-03 13:52 ` Lorenzo Pieralisi
[not found] ` <20170725050237.11033-1-ganapatrao.kulkarni-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
2017-08-15 15:02 ` Robert Richter [this message]
2017-08-15 15:02 ` Robert Richter
2017-08-15 15:02 ` Robert Richter
[not found] ` <20170815150213.GD18024-vWBEXY7mpu582hYKe6nXyg@public.gmane.org>
2017-08-15 15:05 ` Lorenzo Pieralisi
2017-08-15 15:05 ` Lorenzo Pieralisi
2017-08-15 15:05 ` Lorenzo Pieralisi
2017-08-15 16:10 ` Robert Richter
2017-08-15 16:10 ` Robert Richter
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=20170815150213.GD18024@rric.localdomain \
--to=robert.richter-ygcgfspz5w/qt0dzr+alfa@public.gmane.org \
--cc=Will.Deacon-5wv7dgnIgG8@public.gmane.org \
--cc=ganapatrao.kulkarni-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org \
--cc=gklkml16-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jnair-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org \
--cc=lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org \
--cc=lv.zheng-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org \
--cc=sudeep.holla-5wv7dgnIgG8@public.gmane.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.