From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: [GIT pull] irq/urgent for 5.3-rc4
Date: Sat, 10 Aug 2019 20:01:51 -0000 [thread overview]
Message-ID: <156546731194.17538.17579538052592105669.tglx@nanos.tec.linutronix.de> (raw)
In-Reply-To: 156546731194.17538.17422312639927927426.tglx@nanos.tec.linutronix.de
Linus,
please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-urgent-for-linus
up to: 491beed3b102: genirq/affinity: Create affinity mask for single vector
A small fix for the affinity spreading code. It failed to handle situations
where a single vector was requested either due to only one CPU being
available or vector exhaustion causing only a single interrupt to be
granted. The fix is to simply remove the requirement in the affinity
spreading code for more than one interrupt being available.
Thanks,
tglx
------------------>
Ming Lei (1):
genirq/affinity: Create affinity mask for single vector
kernel/irq/affinity.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/kernel/irq/affinity.c b/kernel/irq/affinity.c
index 4352b08ae48d..6fef48033f96 100644
--- a/kernel/irq/affinity.c
+++ b/kernel/irq/affinity.c
@@ -251,11 +251,9 @@ irq_create_affinity_masks(unsigned int nvecs, struct irq_affinity *affd)
* Determine the number of vectors which need interrupt affinities
* assigned. If the pre/post request exhausts the available vectors
* then nothing to do here except for invoking the calc_sets()
- * callback so the device driver can adjust to the situation. If there
- * is only a single vector, then managing the queue is pointless as
- * well.
+ * callback so the device driver can adjust to the situation.
*/
- if (nvecs > 1 && nvecs > affd->pre_vectors + affd->post_vectors)
+ if (nvecs > affd->pre_vectors + affd->post_vectors)
affvecs = nvecs - affd->pre_vectors - affd->post_vectors;
else
affvecs = 0;
next prev parent reply other threads:[~2019-08-10 20:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 20:01 [GIT pull] core/urgent for 5.3-rc4 Thomas Gleixner
2019-08-10 20:01 ` Thomas Gleixner [this message]
2019-08-10 23:20 ` [GIT pull] irq/urgent " pr-tracker-bot
2019-08-10 20:01 ` [GIT pull] sched/urgent " Thomas Gleixner
2019-08-10 23:20 ` pr-tracker-bot
2019-08-10 20:01 ` [GIT pull] x86/urgent " Thomas Gleixner
2019-08-10 23:40 ` pr-tracker-bot
2019-08-10 20:01 ` [GIT pull] perf/urgent " Thomas Gleixner
2019-08-10 23:40 ` pr-tracker-bot
2019-08-10 23:20 ` [GIT pull] core/urgent " pr-tracker-bot
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=156546731194.17538.17579538052592105669.tglx@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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).