From: psodagud@codeaurora.org (Sodagudi Prasad)
To: linux-arm-kernel@lists.infradead.org
Subject: Schedule affinity_notify work while migrating IRQs during hot plug
Date: Mon, 27 Feb 2017 09:12:00 -0800 [thread overview]
Message-ID: <a5b146bd9a36dd7b4fe2bc36cbaadade@codeaurora.org> (raw)
In-Reply-To: <05102c455476941d37904f8c6f387452@codeaurora.org>
On 2017-02-21 12:59, Sodagudi Prasad wrote:
> Hi Thomas,
>
> Currently irq_set_affinity() is called to migrate irqs from
> migrate_one_irq()
> during cpu hot plug and clients which are interested to know the irq
> affinity change
> not getting notified
>
> take_cpu_down () --> __cpu_disable() -->
> irq_migrate_all_off_this_cpu();
>
> irq_set_affinity() is changing the IRQ affinity at chip level
> but it is not notifying the affinity_notify work.
>
Hi Thomas and All,
I could see that in the 3.10 kernel irq affinity notifiers are getting
called when a core getting hot plugged. But in later kernel versions api
used to change
affinity was changed from irq_set_affinity_locked() to
irq_do_set_affinity(), so irq notifiers are not getting called when a
core hot plugged.
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/kernel/irq/manage.c?id=refs/tags/v3.10.105#n201
In latest kernel following path is executed to migrate IRQs.
irq_migrate_all_off_this_cpu() --> migrate_one_irq() ->
irq_do_set_affinity().
As I mentioned above, irq_set_affinity_locked() notifies all clients
drivers, which are registered for IRQ affinity change but
irq_do_set_affinity() API just changes the affinity at irq chip level
but does not notify the clients drivers. I am not sure whether it is
just a miss during IRQ framework refactor or intentionally done like
this. Can you please check whether following code change make sense or
not?
So I am thinking that, adding following sched_work() would notify
clients.
diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index 6b66959..5e4766b 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -207,6 +207,7 @@ int irq_do_set_affinity(struct irq_data *data, const
struct cpumask *mask,
case IRQ_SET_MASK_OK_DONE:
cpumask_copy(desc->irq_common_data.affinity, mask);
case IRQ_SET_MASK_OK_NOCOPY:
+ schedule_work(&desc->affinity_notify->work);
irq_set_thread_affinity(desc);
ret = 0;
}
> How about below change, so that clients drivers gets notified about
> irq affinity changes?
> --- a/kernel/irq/manage.c
> +++ b/kernel/irq/manage.c
> @@ -207,6 +207,7 @@ int irq_do_set_affinity(struct irq_data *data,
> const struct cpumask *mask,
> case IRQ_SET_MASK_OK_DONE:
> cpumask_copy(desc->irq_common_data.affinity, mask);
> case IRQ_SET_MASK_OK_NOCOPY:
> + schedule_work(&desc->affinity_notify->work);
> irq_set_thread_affinity(desc);
> ret = 0;
>
> With this change, notifications of IRQ affinity gets executed and
> notified
> to client drivers.
-Thanks, Prasad
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum,
Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-02-27 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 20:59 Schedule affinity_notify work while migrating IRQs during hot plug Sodagudi Prasad
2017-02-27 17:12 ` Sodagudi Prasad [this message]
2017-02-27 17:21 ` Thomas Gleixner
2017-03-13 19:43 ` Sodagudi Prasad
2017-03-13 20:19 ` Thomas Gleixner
2017-03-17 10:51 ` Sodagudi Prasad
2017-03-17 13:18 ` Thomas Gleixner
2017-03-20 16:36 ` Prasad Sodagudi
2017-03-20 16:36 ` [PATCH] genirq: Notify clients whenever there is change in affinity Prasad Sodagudi
2017-03-23 2:33 ` kbuild test robot
2017-03-23 6:18 ` kbuild test robot
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=a5b146bd9a36dd7b4fe2bc36cbaadade@codeaurora.org \
--to=psodagud@codeaurora.org \
--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).