linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joshua Kinard <kumba@gentoo.org>
To: Paul Burton <paul.burton@imgtec.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	linux-mips@linux-mips.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Jason Cooper <jason@lakedaemon.net>
Subject: Re: [PATCH 0/5] MIPS/irqchip: Use IPI IRQ domains for CPU interrupt controller IPIs
Date: Fri, 31 Mar 2017 17:31:44 -0400	[thread overview]
Message-ID: <24092d33-ae11-f0f4-a390-0add8e3650da@gentoo.org> (raw)
In-Reply-To: <20170330190614.14844-1-paul.burton@imgtec.com>

On 03/30/2017 15:06, Paul Burton wrote:
> This series introduces support for IPI IRQ domains to the CPU interrupt
> controller driver, allowing IPIs to function in the same way as those
> provided by the MIPS GIC as far as platform/board code is concerned.
> 
> Doing this allows us to avoid duplicating code across platforms, avoid
> having to handle cases where IPI domains are or aren't in use depending
> upon the interrupt controller, and strengthen a sanity check for cases
> where IPI IRQ domains are supported.
> 
> Applies atop v4.11-rc4.
> 
> 
> Paul Burton (5):
>   irqchip: mips-cpu: Replace magic 0x100 with IE_SW0
>   irqchip: mips-cpu: Prepare for non-legacy IRQ domains
>   irqchip: mips-cpu: Introduce IPI IRQ domain support
>   MIPS: smp-mt: Use CPU interrupt controller IPI IRQ domain support
>   MIPS: Stengthen IPI IRQ domain sanity check
> 
>  arch/mips/kernel/smp-mt.c       |  49 ++------------
>  arch/mips/kernel/smp.c          |  20 +++---
>  arch/mips/lantiq/irq.c          |  52 --------------
>  arch/mips/mti-malta/malta-int.c |  83 ++---------------------
>  drivers/irqchip/Kconfig         |   2 +
>  drivers/irqchip/irq-mips-cpu.c  | 146 +++++++++++++++++++++++++++++++++++-----
>  6 files changed, 151 insertions(+), 201 deletions(-)

Out of curiosity, "legacy" systems like SGI IP27 (in-tree) and IP30 (external)
support SMP and the IRQ handling is fairly old for IP27 (IP30 borrows IP27's
logic).  Could these systems benefit from using IPI domains?  If so, is there
any kind of crash-course or dummies guide to switching from plain irq_chip to
IPI domains?  Note, both systems have somewhat unique interrupt controllers
built into their system ASICs, but actual IRQ dispatch happens from the CPU
interrupt pins.

Thanks!,

-- 
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
6144R/F5C6C943 2015-04-27
177C 1972 1FB8 F254 BAD0 3E72 5C63 F4E3 F5C6 C943

"The past tempts us, the present confuses us, the future frightens us.  And our
lives slip away, moment by moment, lost in that vast, terrible in-between."

--Emperor Turhan, Centauri Republic

      parent reply	other threads:[~2017-03-31 21:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 19:06 [PATCH 0/5] MIPS/irqchip: Use IPI IRQ domains for CPU interrupt controller IPIs Paul Burton
2017-03-30 19:06 ` Paul Burton
2017-03-30 19:06 ` [PATCH 1/5] irqchip: mips-cpu: Replace magic 0x100 with IE_SW0 Paul Burton
2017-03-30 19:06   ` Paul Burton
2017-03-30 19:06 ` [PATCH 2/5] irqchip: mips-cpu: Prepare for non-legacy IRQ domains Paul Burton
2017-03-30 19:06   ` Paul Burton
2017-03-30 19:06 ` [PATCH 3/5] irqchip: mips-cpu: Introduce IPI IRQ domain support Paul Burton
2017-03-30 19:06   ` Paul Burton
2017-03-30 19:06 ` [PATCH 4/5] MIPS: smp-mt: Use CPU interrupt controller " Paul Burton
2017-03-30 19:06   ` Paul Burton
2017-03-30 19:06 ` [PATCH 5/5] MIPS: Stengthen IPI IRQ domain sanity check Paul Burton
2017-03-30 19:06   ` Paul Burton
2017-03-31  9:02 ` [PATCH 0/5] MIPS/irqchip: Use IPI IRQ domains for CPU interrupt controller IPIs Thomas Gleixner
2017-04-12 21:14   ` Ralf Baechle
2017-03-31 21:31 ` Joshua Kinard [this message]

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=24092d33-ae11-f0f4-a390-0add8e3650da@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=jason@lakedaemon.net \
    --cc=linux-mips@linux-mips.org \
    --cc=marc.zyngier@arm.com \
    --cc=paul.burton@imgtec.com \
    --cc=ralf@linux-mips.org \
    --cc=tglx@linutronix.de \
    /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).