public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Marc Zyngier <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: gregory.clement@free-electrons.com, james.hogan@imgtec.com,
	paul.burton@imgtec.com, andrew@lunn.ch, cernekee@gmail.com,
	linux-kernel@vger.kernel.org, jason@lakedaemon.net,
	chris@zankel.net, f.fainelli@gmail.com,
	sebastian.hesselbarth@gmail.com, mingo@kernel.org,
	jcmvbkbc@gmail.com, xuwei5@hisilicon.com, tglx@linutronix.de,
	hpa@zytor.com, marc.zyngier@arm.com, matt.redfearn@imgtec.com
Subject: [tip:irq/core] irqchip/gic-v3-its: Report that effective affinity is a single target
Date: Fri, 18 Aug 2017 01:59:14 -0700	[thread overview]
Message-ID: <tip-0d224d3508f5ba67438b921fc37cf179c9652f20@git.kernel.org> (raw)
In-Reply-To: <20170818083925.10108-6-marc.zyngier@arm.com>

Commit-ID:  0d224d3508f5ba67438b921fc37cf179c9652f20
Gitweb:     http://git.kernel.org/tip/0d224d3508f5ba67438b921fc37cf179c9652f20
Author:     Marc Zyngier <marc.zyngier@arm.com>
AuthorDate: Fri, 18 Aug 2017 09:39:18 +0100
Committer:  Thomas Gleixner <tglx@linutronix.de>
CommitDate: Fri, 18 Aug 2017 10:54:40 +0200

irqchip/gic-v3-its: Report that effective affinity is a single target

The GICv3 ITS driver only targets a single CPU at a time, even if
the notional affinity is wider. Let's inform the core code
about this.

Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Andrew Lunn <andrew@lunn.ch>
Cc: James Hogan <james.hogan@imgtec.com>
Cc: Jason Cooper <jason@lakedaemon.net>
Cc: Paul Burton <paul.burton@imgtec.com>
Cc: Chris Zankel <chris@zankel.net>
Cc: Kevin Cernekee <cernekee@gmail.com>
Cc: Wei Xu <xuwei5@hisilicon.com>
Cc: Max Filippov <jcmvbkbc@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>
Cc: Gregory Clement <gregory.clement@free-electrons.com>
Cc: Matt Redfearn <matt.redfearn@imgtec.com>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Link: http://lkml.kernel.org/r/20170818083925.10108-6-marc.zyngier@arm.com

---
 drivers/irqchip/irq-gic-v3-its.c | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
index 6893287..22e2285 100644
--- a/drivers/irqchip/irq-gic-v3-its.c
+++ b/drivers/irqchip/irq-gic-v3-its.c
@@ -649,6 +649,7 @@ static int its_set_affinity(struct irq_data *d, const struct cpumask *mask_val,
 		target_col = &its_dev->its->collections[cpu];
 		its_send_movi(its_dev, target_col, id);
 		its_dev->event_map.col_map[id] = cpu;
+		irq_data_update_effective_affinity(d, cpumask_of(cpu));
 	}
 
 	return IRQ_SET_MASK_OK_DONE;
@@ -1481,6 +1482,7 @@ static int its_irq_domain_alloc(struct irq_domain *domain, unsigned int virq,
 
 		irq_domain_set_hwirq_and_chip(domain, virq + i,
 					      hwirq, &its_irq_chip, its_dev);
+		irqd_set_single_target(irq_desc_get_irq_data(irq_to_desc(virq + i)));
 		pr_debug("ID:%d pID:%d vID:%d\n",
 			 (int)(hwirq - its_dev->event_map.lpi_base),
 			 (int) hwirq, virq + i);
@@ -1495,13 +1497,16 @@ static void its_irq_domain_activate(struct irq_domain *domain,
 	struct its_device *its_dev = irq_data_get_irq_chip_data(d);
 	u32 event = its_get_event_id(d);
 	const struct cpumask *cpu_mask = cpu_online_mask;
+	int cpu;
 
 	/* get the cpu_mask of local node */
 	if (its_dev->its->numa_node >= 0)
 		cpu_mask = cpumask_of_node(its_dev->its->numa_node);
 
 	/* Bind the LPI to the first possible CPU */
-	its_dev->event_map.col_map[event] = cpumask_first(cpu_mask);
+	cpu = cpumask_first(cpu_mask);
+	its_dev->event_map.col_map[event] = cpu;
+	irq_data_update_effective_affinity(d, cpumask_of(cpu));
 
 	/* Map the GIC IRQ and event to the device */
 	its_send_mapti(its_dev, d->hwirq, event);

  reply	other threads:[~2017-08-18  9:03 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 ` [PATCH v2 01/12] genirq: Restrict effective affinity to interrupts actually using it Marc Zyngier
2017-08-18  8:57   ` [tip:irq/core] " 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-bot for Marc Zyngier [this message]
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=tip-0d224d3508f5ba67438b921fc37cf179c9652f20@git.kernel.org \
    --to=tipbot@zytor.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=hpa@zytor.com \
    --cc=james.hogan@imgtec.com \
    --cc=jason@lakedaemon.net \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=matt.redfearn@imgtec.com \
    --cc=mingo@kernel.org \
    --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