From: Marc Zyngier <marc.zyngier@arm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Heyi Guo <guoheyi@huawei.com>, Heyi Guo <heyi.guo@linaro.org>,
Lubomir Rintel <lkundrak@v3.sk>, Pavel Machek <pavel@ucw.cz>,
Zenghui Yu <yuzenghui@huawei.com>,
Zheng Xiang <zhengxiang9@huawei.com>,
Jason Cooper <jason@lakedaemon.net>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] irqchip updates for 5.0-rc6
Date: Wed, 6 Feb 2019 10:48:43 +0000 [thread overview]
Message-ID: <20190206104848.12580-1-marc.zyngier@arm.com> (raw)
Hi Thomas,
This is the final set of 5.0 updates from the irqchip department. This
time, an embarassingly large number of GICv3/GICv4 buglets (VLPI drop,
MSI allocation race on device sharing the same DevID, LPI pool
exhaustion and other cleanups), as well as a fix for PJ4-based systems
that apparently never worked correctly until now.
Please pull,
M.
The following changes since commit 8208d1708b88b412ca97f50a6d951242c88cbbac:
irqchip/gic-v3-its: Align PCI Multi-MSI allocation on their size (2019-01-18 14:35:38 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git tags/irqchip-5.0-3
for you to fetch changes up to 56841070ccc87b463ac037d2d1f2beb8e5e35f0c:
irqchip/gic-v3-its: Fix ITT_entry_size accessor (2019-01-31 12:51:33 +0000)
----------------------------------------------------------------
irqchip update for 5.0-rc6
- Another GICv3 ITS fix for devices sharing the same DevID
- Don't return invalid data on exhaustion of the GICv3 LPI pool
- Fix a GICv3 field decoding bug leading to memory over-allocation
- Init GICv4 at boot time instead of lazy init
- Fix interrupt masking on PJ4
----------------------------------------------------------------
Heyi Guo (1):
irqchip/gic-v4: Fix occasional VLPI drop
Lubomir Rintel (1):
irqchip/mmp: Only touch the PJ4 IRQ & FIQ bits on enable/disable
Marc Zyngier (2):
irqchip/gic-v3-its: Plug allocation race for devices sharing a DevID
irqchip/gic-v3-its: Gracefully fail on LPI exhaustion
Zenghui Yu (1):
irqchip/gic-v3-its: Fix ITT_entry_size accessor
drivers/irqchip/irq-gic-v3-its.c | 101 +++++++++++++++++++++++++++++--------
drivers/irqchip/irq-mmp.c | 6 ++-
include/linux/irqchip/arm-gic-v3.h | 2 +-
3 files changed, 85 insertions(+), 24 deletions(-)
next reply other threads:[~2019-02-06 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 10:48 Marc Zyngier [this message]
2019-02-06 10:48 ` [PATCH 1/5] irqchip/gic-v4: Fix occasional VLPI drop Marc Zyngier
2019-02-06 10:48 ` [PATCH 2/5] irqchip/gic-v3-its: Plug allocation race for devices sharing a DevID Marc Zyngier
2019-02-06 10:48 ` [PATCH 3/5] irqchip/gic-v3-its: Gracefully fail on LPI exhaustion Marc Zyngier
2019-02-06 10:48 ` [PATCH 4/5] irqchip/mmp: Only touch the PJ4 IRQ & FIQ bits on enable/disable Marc Zyngier
2019-02-06 10:48 ` [PATCH 5/5] irqchip/gic-v3-its: Fix ITT_entry_size accessor Marc Zyngier
2019-02-06 10:57 ` [PATCH 0/5] irqchip updates for 5.0-rc6 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=20190206104848.12580-1-marc.zyngier@arm.com \
--to=marc.zyngier@arm.com \
--cc=guoheyi@huawei.com \
--cc=heyi.guo@linaro.org \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=pavel@ucw.cz \
--cc=tglx@linutronix.de \
--cc=yuzenghui@huawei.com \
--cc=zhengxiang9@huawei.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®