From: robert.richter@caviumnetworks.com (Robert Richter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] irqchip, gicv3-its, numa: Workaround for Cavium thunderx erratum 23144
Date: Wed, 17 Feb 2016 13:16:05 +0100 [thread overview]
Message-ID: <20160217121605.GE24726@rric.localdomain> (raw)
In-Reply-To: <1455628282-8939-1-git-send-email-gkulkarni@caviumnetworks.com>
On 16.02.16 18:41:22, Ganapatrao Kulkarni wrote:
> The erratum fixes the hang of ITS SYNC command by avoiding inter node
> io and collections/cpu mapping on thunderx dual-socket platform.
>
> This is based on NUMA v10 series.
> https://lkml.org/lkml/2016/2/2/134
>
> v3:
> updatated as per Marc Zyngier's review comments.
> http://www.spinics.net/lists/arm-kernel/msg443462.html
>
> v2:
> updatated as per Marc Zyngier's review comments.
>
> Signed-off-by: Ganapatrao Kulkarni <gkulkarni@caviumnetworks.com>
>
> ---
> arch/arm64/Kconfig | 9 ++++++++
> drivers/irqchip/irq-gic-v3-its.c | 46 ++++++++++++++++++++++++++++++++++++++--
> 2 files changed, 53 insertions(+), 2 deletions(-)
> @@ -1086,6 +1098,14 @@ static void its_cpu_init_collection(void)
> list_for_each_entry(its, &its_nodes, entry) {
> u64 target;
>
> + /* avoid cross node collections and its mapping */
> + if (its->flags & ITS_FLAGS_WORKAROUND_CAVIUM_23144) {
> + struct device_node *cpu_node;
> + cpu_node = of_get_cpu_node(cpu, NULL);
> + if (its->numa_node != of_node_to_nid(cpu_node))
> + continue;
I think you may not continue in case of its->numa_node ==
NUMA_NO_NODE. This is the case if no numa node info is provided and
thus ITS is systemwide. So the check needs to be extended accordingly.
-Robert
> + }
> +
> /*
> * We now have to bind each collection to its target
> * redistributor.
prev parent reply other threads:[~2016-02-17 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 13:11 [PATCH v3] irqchip, gicv3-its, numa: Workaround for Cavium thunderx erratum 23144 Ganapatrao Kulkarni
2016-02-17 12:16 ` Robert Richter [this message]
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=20160217121605.GE24726@rric.localdomain \
--to=robert.richter@caviumnetworks.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