From: Sodagudi Prasad <psodagud@codeaurora.org>
To: tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, james.morse@arm.com,
will.deacon@arm.com, catalin.marinas@arm.com
Subject: Schedule affinity_notify work while migrating IRQs during hot plug
Date: Tue, 21 Feb 2017 12:59:13 -0800 [thread overview]
Message-ID: <05102c455476941d37904f8c6f387452@codeaurora.org> (raw)
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.
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.
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum,
Linux Foundation Collaborative Project
next reply other threads:[~2017-02-21 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 20:59 Sodagudi Prasad [this message]
2017-02-27 17:12 ` Schedule affinity_notify work while migrating IRQs during hot plug Sodagudi Prasad
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=05102c455476941d37904f8c6f387452@codeaurora.org \
--to=psodagud@codeaurora.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
/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).