From: Marc Zyngier <marc.zyngier@arm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Wei Xu <xuwei5@hisilicon.com>,
James Hogan <james.hogan@imgtec.com>,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@free-electrons.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Kevin Cernekee <cernekee@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Chris Zankel <chris@zankel.net>,
Max Filippov <jcmvbkbc@gmail.com>,
Paul Burton <paul.burton@imgtec.com>,
Matt Redfearn <matt.redfearn@imgtec.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 01/12] genirq: Restrict effective affinity to interrupts actually using it
Date: Fri, 18 Aug 2017 09:39:14 +0100 [thread overview]
Message-ID: <20170818083925.10108-2-marc.zyngier@arm.com> (raw)
In-Reply-To: <20170818083925.10108-1-marc.zyngier@arm.com>
Just because CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK is selected
doesn't mean that all the interrupts are using the effective
affinity mask. For a number of them, this mask is likely to
be empty.
In order to deal with this, let's restrict the use of the
effective affinity mask to these interrupts that have a non empty
effective affinity.
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
---
include/linux/irq.h | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/include/linux/irq.h b/include/linux/irq.h
index d2d543794093..dcfac6c8ba18 100644
--- a/include/linux/irq.h
+++ b/include/linux/irq.h
@@ -781,7 +781,10 @@ static inline struct cpumask *irq_data_get_affinity_mask(struct irq_data *d)
static inline
struct cpumask *irq_data_get_effective_affinity_mask(struct irq_data *d)
{
- return d->common->effective_affinity;
+ if (!cpumask_empty(d->common->effective_affinity))
+ return d->common->effective_affinity;
+
+ return d->common->affinity;
}
static inline void irq_data_update_effective_affinity(struct irq_data *d,
const struct cpumask *m)
--
2.11.0
next prev parent reply other threads:[~2017-08-18 8:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 8:39 [PATCH v2 00/12] genirq/irqchip: Effective affinity fixups Marc Zyngier
2017-08-18 8:39 ` Marc Zyngier [this message]
2017-08-18 8:57 ` [tip:irq/core] genirq: Restrict effective affinity to interrupts actually using it tip-bot for Marc Zyngier
2017-08-18 8:39 ` [PATCH v2 02/12] genirq/proc: Use the the accessor to report the effective affinity Marc Zyngier
2017-08-18 8:58 ` [tip:irq/core] " tip-bot for Marc Zyngier
2017-08-18 8:39 ` [PATCH v2 03/12] irqchip/gic: Report that effective affinity is a single target Marc Zyngier
2017-08-18 8:58 ` [tip:irq/core] " tip-bot for Marc Zyngier
2017-08-18 8:39 ` [PATCH v2 04/12] irqchip/gic-v3: " Marc Zyngier
2017-08-18 8:58 ` [tip:irq/core] " tip-bot for Marc Zyngier
2017-08-18 8:39 ` [PATCH v2 05/12] irqchip/gic-v3-its: " Marc Zyngier
2017-08-18 8:59 ` [tip:irq/core] " tip-bot for Marc Zyngier
2017-08-18 8:39 ` [PATCH v2 06/12] irqchip/armada-370-xp: " Marc Zyngier
2017-08-18 8:59 ` [tip:irq/core] " tip-bot for Marc Zyngier
2017-08-18 8:39 ` [PATCH v2 07/12] irqchip/bcm-6345-l1: " Marc Zyngier
2017-08-18 9:00 ` [tip:irq/core] " tip-bot for Marc Zyngier
2017-08-18 8:39 ` [PATCH v2 08/12] irqchip/bcm-7038-l1: " Marc Zyngier
2017-08-18 9:00 ` [tip:irq/core] " tip-bot for Marc Zyngier
2017-08-18 8:39 ` [PATCH v2 09/12] irqchip/metag-ext: " Marc Zyngier
2017-08-18 9:00 ` [tip:irq/core] " tip-bot for Marc Zyngier
2017-08-18 8:39 ` [PATCH v2 10/12] irqchip/hip04: " Marc Zyngier
2017-08-18 9:01 ` [tip:irq/core] " tip-bot for Marc Zyngier
2017-08-18 8:39 ` [PATCH v2 11/12] irqchip/mips-gic: " Marc Zyngier
2017-08-18 9:01 ` [tip:irq/core] " tip-bot for Marc Zyngier
2017-08-18 8:39 ` [PATCH v2 12/12] irqchip/xtensa-mx: " Marc Zyngier
2017-08-18 9:01 ` [tip:irq/core] " tip-bot for Marc Zyngier
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=20170818083925.10108-2-marc.zyngier@arm.com \
--to=marc.zyngier@arm.com \
--cc=andrew@lunn.ch \
--cc=cernekee@gmail.com \
--cc=chris@zankel.net \
--cc=f.fainelli@gmail.com \
--cc=gregory.clement@free-electrons.com \
--cc=james.hogan@imgtec.com \
--cc=jason@lakedaemon.net \
--cc=jcmvbkbc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.redfearn@imgtec.com \
--cc=paul.burton@imgtec.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tglx@linutronix.de \
--cc=xuwei5@hisilicon.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
all inboxes | Powered by JetHome®