From: Srinivas Ramana <sramana@codeaurora.org>
To: tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] genirq: Make sure the affinity to be set is not empty
Date: Wed, 2 Jan 2019 12:29:33 +0530 [thread overview]
Message-ID: <45756028-c96f-e3b5-389d-d8f022c59c5d@codeaurora.org> (raw)
In-Reply-To: <1545312957-8504-1-git-send-email-sramana@codeaurora.org>
On 12/20/2018 7:05 PM, Srinivas Ramana wrote:
> If the default_affinity is managed/initialized by a system and
> all the cpus present in irq_default_affinity are hotplugged out
> we may end up passing a cpumask of 0 to irq_do_set_affinity().
>
> Fix this by falling back to cpu_online_mask in case the
> calculated affinity becomes zero.
>
> Signed-off-by: Srinivas Ramana <sramana@codeaurora.org>
> ---
> kernel/irq/manage.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
> index 9dbdccab3b6a..5c0ba5ca5930 100644
> --- a/kernel/irq/manage.c
> +++ b/kernel/irq/manage.c
> @@ -393,6 +393,9 @@ int irq_setup_affinity(struct irq_desc *desc)
> }
>
> cpumask_and(&mask, cpu_online_mask, set);
> + if (cpumask_empty(&mask))
> + cpumask_copy(&mask, cpu_online_mask);
> +
> if (node != NUMA_NO_NODE) {
> const struct cpumask *nodemask = cpumask_of_node(node);
>
>
Hi,
Can you provide your feedback on this?
Thanks,
-- Srinivas R
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation
Center, Inc., is a member of Code Aurora Forum, a Linux Foundation
Collaborative Project
next prev parent reply other threads:[~2019-01-02 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 13:35 Srinivas Ramana
2019-01-02 6:59 ` Srinivas Ramana [this message]
2019-01-15 10:27 ` [tip:irq/urgent] genirq: Make sure the initial affinity " tip-bot for Srinivas Ramana
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=45756028-c96f-e3b5-389d-d8f022c59c5d@codeaurora.org \
--to=sramana@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome