From: Marc Zyngier <maz@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Doug Anderson <dianders@chromium.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Stephen Boyd <swboyd@chromium.org>,
Valentin Schneider <vschneid@redhat.com>,
Chen-Yu Tsai <wenst@chromium.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
D Scott Phillips <scott@os.amperecomputing.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Misono Tomohiro <misono.tomohiro@fujitsu.com>,
Peter Zijlstra <peterz@infradead.org>,
Sumit Garg <sumit.garg@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/2] arm64: smp: Fix pseudo NMI issues w/ broken Mediatek FW
Date: Fri, 06 Oct 2023 11:20:44 +0100 [thread overview]
Message-ID: <864jj4njb7.wl-maz@kernel.org> (raw)
In-Reply-To: <ZR6Pjk_3gpx1K3pF@FVFF77S0Q05N>
On Thu, 05 Oct 2023 11:27:26 +0100,
Mark Rutland <mark.rutland@arm.com> wrote:
> 3) Partial fix: make the ARM64_HAS_GIC_PRIO_MASKING cpucap depend on the
> absence of a "mediatek,broken-save-restore-fw" property in the DT. I believe
> we can check that in early_enable_pseudo_nmi() or can_use_gic_priorities().
>
> That'll avoid potential issues if/when we change the priorities used for
> pNMI (which is something I've been looking at).
>
> I'm happy with (3) if Marc is.
Definitely worth investigating if you have the bandwidth.
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-06 10:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 16:45 [PATCH 1/2] arm64: smp: Fix pseudo NMI issues w/ broken Mediatek FW Douglas Anderson
2023-10-02 16:45 ` [PATCH 2/2] arm64: smp: Don't directly call arch_smp_send_reschedule() for wakeup Douglas Anderson
2023-10-02 17:25 ` Mark Rutland
2023-10-02 17:24 ` [PATCH 1/2] arm64: smp: Fix pseudo NMI issues w/ broken Mediatek FW Mark Rutland
2023-10-02 19:16 ` Doug Anderson
2023-10-03 12:29 ` Mark Rutland
2023-10-03 13:43 ` Doug Anderson
2023-10-03 16:32 ` Mark Rutland
2023-10-03 19:32 ` Doug Anderson
2023-10-04 9:59 ` Mark Rutland
2023-10-04 10:15 ` Marc Zyngier
2023-10-04 14:04 ` Doug Anderson
2023-10-05 10:27 ` Mark Rutland
2023-10-05 15:34 ` Doug Anderson
2023-10-06 12:19 ` Catalin Marinas
2023-10-06 10:20 ` Marc Zyngier [this message]
2023-10-06 22:17 ` Doug Anderson
2023-10-06 9:55 ` Marc Zyngier
2023-10-06 10:20 ` Chen-Yu Tsai
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=864jj4njb7.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=catalin.marinas@arm.com \
--cc=dianders@chromium.org \
--cc=jpoimboe@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=misono.tomohiro@fujitsu.com \
--cc=peterz@infradead.org \
--cc=scott@os.amperecomputing.com \
--cc=sumit.garg@linaro.org \
--cc=swboyd@chromium.org \
--cc=tglx@linutronix.de \
--cc=vschneid@redhat.com \
--cc=wenst@chromium.org \
--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;
as well as URLs for NNTP newsgroup(s).