From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.cs.columbia.edu,
Alexandru Elisei <alexandru.elisei@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: will@kernel.org, jason@lakedaemon.net, tglx@linutronix.de,
catalin.marinas@arm.com
Subject: Re: [PATCH v3 0/2] irqchip/gic-v3: Support pseudo-NMIs when SCR_EL3.FIQ == 0
Date: Sun, 13 Sep 2020 18:05:15 +0100 [thread overview]
Message-ID: <160001658182.6915.9030793517863303185.b4-ty@kernel.org> (raw)
In-Reply-To: <20200912153707.667731-1-alexandru.elisei@arm.com>
On Sat, 12 Sep 2020 16:37:05 +0100, Alexandru Elisei wrote:
> Trusted Firmware-A's default interrupt routing model is to clear
> SCR_EL3.FIQ, which is the only case that GICv3 doesn't support. This series
> tries to fix that by detecting it at runtime and using a different priority
> value for ICC_PMR_EL1 when masking regular interrupts. As a result, we will
> be able to support pseudo-NMIs on all combinations of GIC security states
> and firmware configurations.
>
> [...]
Applied to irq/irqchip-next, thanks!
[1/2] irqchip/gic-v3: Spell out when pseudo-NMIs are enabled
commit: 4e594ad1068ea1db359d6161f580f03edecf6cb0
[2/2] irqchip/gic-v3: Support pseudo-NMIs when SCR_EL3.FIQ == 0
commit: 336780590990efa69596884114cad3f517b6333b
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2020-09-13 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 15:37 Alexandru Elisei
2020-09-12 15:37 ` [PATCH v3 1/2] irqchip/gicv3: Spell out when pseudo-NMIs are enabled Alexandru Elisei
2020-10-11 17:57 ` [tip: irq/core] irqchip/gic-v3: " tip-bot2 for Alexandru Elisei
2020-09-12 15:37 ` [PATCH v3 2/2] irqchip/gic-v3: Support pseudo-NMIs when SCR_EL3.FIQ == 0 Alexandru Elisei
2020-10-11 17:57 ` [tip: irq/core] " tip-bot2 for Alexandru Elisei
2020-09-13 17:05 ` Marc Zyngier [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=160001658182.6915.9030793517863303185.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=catalin.marinas@arm.com \
--cc=jason@lakedaemon.net \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.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
all inboxes | Powered by JetHome®