From: Marc Zyngier <maz@kernel.org>
To: Valentin Schneider <valentin.schneider@arm.com>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
kernel-team@android.com, Steev Klimaszewski <steev@kali.org>
Subject: Re: [PATCH] irqchip/gic-v3-its: Skip HP notifier when no ITS is registered
Date: Wed, 02 Feb 2022 13:30:08 +0000 [thread overview]
Message-ID: <ac5a68d5d2479b1bdfa3a5bfc8c35033@kernel.org> (raw)
In-Reply-To: <87pmo5o2j7.mognet@arm.com>
On 2022-02-02 12:50, Valentin Schneider wrote:
> On 02/02/22 10:34, Marc Zyngier wrote:
>> We have some systems out there that have both LPI support and an
>> ITS, but that don't expose the ITS in their firmware tables
>> (either because it is broken or because they run under a hypervisor
>> that hides it...).
>>
>
> Huh :)
Yeah. Got to love these WoA machines where EL2 hides most of the
useful HW, but also can't be bothered to consistently emulate
the registers they trap (cue the bug that was causing the SMMUv2
driver to explode on store of xzr to an MMIO register). Bah.
>
>> Is such a configuration, we still register the HP notifier to free
>> the allocated tables if needed, resulting in a warning as there is
>> no memory to free (nothing was allocated the first place).
>>
>
> Right, so list_empty(&its_nodes) means no ->pend_page, but still having
> the
> HP notifier means we hit the WARN_ON(!pend_page).
>
>> Fix it by keying the HP notifier on the presence of at least one
>> sucessfully probed ITS.
>>
>
> That looks fine to me.
>
> Reviewed-by: Valentin Schneider <valentin.schneider@arm.com>
Thanks,
M.
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2022-02-02 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 10:34 [PATCH] irqchip/gic-v3-its: Skip HP notifier when no ITS is registered Marc Zyngier
2022-02-02 10:40 ` Steev Klimaszewski
2022-02-02 10:46 ` [irqchip: irq/irqchip-fixes] " irqchip-bot for Marc Zyngier
2022-02-02 12:50 ` [PATCH] " Valentin Schneider
2022-02-02 13:30 ` 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=ac5a68d5d2479b1bdfa3a5bfc8c35033@kernel.org \
--to=maz@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steev@kali.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