From: rrichter@cavium.com (Robert Richter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/9] irqchip/gic-v3-its: Implement ITS nodes as kernel devices and use CMA
Date: Wed, 1 Feb 2017 18:38:24 +0100 [thread overview]
Message-ID: <20170201173833.12630-1-rrichter@cavium.com> (raw)
This patch series implements ITS nodes as kernel devices. The
advantage of that is that CMA can be used to allocate large ITS
tables, where standard memory and page allocation fails (above
MAX_ORDER - 1). This approach was suggested first here:
https://marc.info/?i=56D44812.6000309%40arm.com
Another advantage is that all memory resources of the device are now
device managed, thus the code for releasing the device becomes much
easier.
The following is required to implement this:
* each ITS node must be assigned to a struct device each,
* the ITS initialization must be moved to a later point during boot,
* the ITS enablement must be separated from the GIC code (the GIC
still needs to be enabled early),
* the early ITS node probing by DT or ACPI must be separated from the
ITS initialization,
* ITS table allocation must be changed to use dma_alloc_coherent()
which uses CMA for allocation of large memory ranges.
The patches of this series implement this.
The first patch is a fix and should be marked stable.
Robert Richter (9):
irqchip/gic-v3-its: Fix command buffer allocation
irqchip/gic-v3-its: Initialize its nodes in probe order
irqchip/gic-v3-its: Initialize MSIs with subsys_initcalls
irqchip/gic-v3-its: Split probing from its node initialization
irqchip/gic-v3-its: Decouple its initialization from gic
irqchip/gic-v3-its: Prevent its init ordering dependencies
irqchip/gic-v3-its: Initialize its nodes later
irqchip/gic-v3-its: Handle its nodes as kernel devices
irqchip, gicv3-its, cma: Use CMA for allocation of large device tables
drivers/irqchip/irq-gic-v3-its-pci-msi.c | 6 +-
drivers/irqchip/irq-gic-v3-its-platform-msi.c | 6 +-
drivers/irqchip/irq-gic-v3-its.c | 273 ++++++++++++++++----------
drivers/irqchip/irq-gic-v3.c | 8 +-
include/linux/cpuhotplug.h | 1 +
include/linux/irqchip/arm-gic-v3.h | 5 +-
6 files changed, 184 insertions(+), 115 deletions(-)
--
2.11.0
next reply other threads:[~2017-02-01 17:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 17:38 Robert Richter [this message]
2017-02-01 17:38 ` [PATCH 1/9] irqchip/gic-v3-its: Fix command buffer allocation Robert Richter
2017-02-08 14:41 ` Marc Zyngier
2017-02-08 14:43 ` Robert Richter
2017-02-08 15:31 ` Shanker Donthineni
2017-02-08 15:36 ` Robert Richter
2017-02-08 16:00 ` Marc Zyngier
2017-02-08 15:45 ` Marc Zyngier
2017-02-01 17:38 ` [PATCH 2/9] irqchip/gic-v3-its: Initialize its nodes in probe order Robert Richter
2017-02-01 17:38 ` [PATCH 3/9] irqchip/gic-v3-its: Initialize MSIs with subsys_initcalls Robert Richter
2017-02-01 17:38 ` [PATCH 4/9] irqchip/gic-v3-its: Split probing from its node initialization Robert Richter
2017-02-01 17:38 ` [PATCH 5/9] irqchip/gic-v3-its: Decouple its initialization from gic Robert Richter
2017-02-01 17:38 ` [PATCH 6/9] irqchip/gic-v3-its: Prevent its init ordering dependencies Robert Richter
2017-02-01 17:38 ` [PATCH 7/9] irqchip/gic-v3-its: Initialize its nodes later Robert Richter
2017-02-01 17:38 ` [PATCH 8/9] irqchip/gic-v3-its: Handle its nodes as kernel devices Robert Richter
2017-02-01 17:38 ` [PATCH 9/9] irqchip, gicv3-its, cma: Use CMA for allocation of large device tables Robert Richter
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=20170201173833.12630-1-rrichter@cavium.com \
--to=rrichter@cavium.com \
--cc=linux-arm-kernel@lists.infradead.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