public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Gregory Clement <gregory.clement@bootlin.com>,
	Jason Cooper <jason@lakedaemon.net>,
	Laurentiu Tudor <laurentiu.tudor@nxp.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Valentin Schneider <valentin.schneider@arm.com>
Subject: [PATCH 0/9] irqchip/gic: generalize use of HW-based retriggering
Date: Mon, 24 Aug 2020 11:23:08 +0100	[thread overview]
Message-ID: <20200824102317.1038259-1-maz@kernel.org> (raw)

Valentin recently pointed out that that relying on SW-based retrigger
with any of the GIC interrupt controller is both inefficient and
slightly broken, as it messes the GIC's own state machine.

In order to move the GIC over to use its natural HW-based triggering
mechanism, we need to teach all the stacked interrupt controllers that
can pile on a GIC to use the hierarchy-based retrigger helper. This
includes the bus-specific irqchips, such as PCI, FSL-MC, and the funky
platform-MSI.

Marc Zyngier (7):
  irqchip/git-v3-its: Implement irq_retrigger callback for
    device-triggered LPIs
  PCI/MSI: Provide default retrigger callback
  platform-msi: Provide default retrigger callback
  fsl-msi: Provide default retrigger callback
  irqchip/mbigen: Use hierarchy retrigger helper
  irqchip/mvebu-icu: Use hierarchy retrigger helper
  irqchip/mvebu-sei: Use hierarchy retrigger helper

Valentin Schneider (2):
  irqchip/gic-v2, v3: Implement irq_chip->irq_retrigger()
  irqchip/gic-v2, v3: Prevent SW resends entirely

 drivers/base/platform-msi.c      |  2 ++
 drivers/bus/fsl-mc/fsl-mc-msi.c  |  2 ++
 drivers/irqchip/irq-gic-v3-its.c |  6 ++++++
 drivers/irqchip/irq-gic-v3.c     | 12 +++++++++++-
 drivers/irqchip/irq-gic.c        | 12 +++++++++++-
 drivers/irqchip/irq-mbigen.c     |  1 +
 drivers/irqchip/irq-mvebu-icu.c  |  2 ++
 drivers/irqchip/irq-mvebu-sei.c  |  2 ++
 drivers/pci/msi.c                |  2 ++
 9 files changed, 39 insertions(+), 2 deletions(-)

-- 
2.27.0


             reply	other threads:[~2020-08-24 10:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 10:23 Marc Zyngier [this message]
2020-08-24 10:23 ` [PATCH 1/9] irqchip/gic-v2, v3: Implement irq_chip->irq_retrigger() Marc Zyngier
2020-08-24 10:23 ` [PATCH 2/9] irqchip/git-v3-its: Implement irq_retrigger callback for device-triggered LPIs Marc Zyngier
2020-08-24 10:23 ` [PATCH 3/9] PCI/MSI: Provide default retrigger callback Marc Zyngier
2020-08-25 19:44   ` Bjorn Helgaas
2020-08-24 10:23 ` [PATCH 4/9] platform-msi: " Marc Zyngier
2020-08-24 10:23 ` [PATCH 5/9] fsl-msi: " Marc Zyngier
2020-08-26 11:16   ` Valentin Schneider
2020-08-26 16:37     ` Marc Zyngier
2020-08-26 17:52       ` Marc Zyngier
2020-08-24 10:23 ` [PATCH 6/9] irqchip/mbigen: Use hierarchy retrigger helper Marc Zyngier
2020-08-24 10:23 ` [PATCH 7/9] irqchip/mvebu-icu: " Marc Zyngier
2020-08-24 10:23 ` [PATCH 8/9] irqchip/mvebu-sei: " Marc Zyngier
2020-08-24 10:23 ` [PATCH 9/9] irqchip/gic-v2, v3: Prevent SW resends entirely 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=20200824102317.1038259-1-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=gregory.clement@bootlin.com \
    --cc=jason@lakedaemon.net \
    --cc=laurentiu.tudor@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=valentin.schneider@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