From: Marc Zyngier <maz@kernel.org>
To: Abel Vesa <abel.vesa@oss.qualcomm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Abel Vesa <abelvesa@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Mostafa Saleh <smostafa@google.com>
Subject: Re: [PATCH] interconnect: qcom: icc-rpmh: Add opt-out parameter for QoS settings
Date: Mon, 07 Sep 2026 22:15:09 +0100 [thread overview]
Message-ID: <87ld9c4vc2.wl-maz@kernel.org> (raw)
In-Reply-To: <v2gxqazjoxe74q5364jucy4pjds6gx4gfdchgulekl5mwk2azk@we4ibolioibm>
On Mon, 07 Sep 2026 21:21:44 +0100,
Abel Vesa <abel.vesa@oss.qualcomm.com> wrote:
>
> On 26-09-07 18:17:29, Marc Zyngier wrote:
> > Recent addition of QoS configuration to the X1 variants resulted in
> > systems that spontaneously reset at boot time or under load.
> >
> > Given that this is both very unpleasant and hard to debug, give the
> > affected user the option to survive such event with a module parameter.
> >
> > Passing "icc_rpmh.enable_qos=0" to the kernel command-line will skip the
> > offending QoS setup.
> >
>
> Lets not start doing this, please.
>
> Can we figure out which platform deosn't work and then maybe we can
> add a quirk in DT per platform?
We have at least 3 machines that are dysfunctional since [1] was
merged (mini-x, sp12 and devkit). Probably some more, but I'm not
going to be the one doing a survey.
What really should happen is [1] to be reversed until QC figures out a
set of parameters that actually works, instead of making this platform
even more unreliable than it already is.
Just like [2] should have been reverted.
Until then, we'll have to paper over this stuff.
M.
[1] https://lore.kernel.org/all/20260527-x1e80100_qos-v2-2-305c6539e6d2@oss.qualcomm.com
[2] https://lore.kernel.org/all/20260203063244.1498699-1-xin.liu@oss.qualcomm.com
--
Jazz isn't dead. It just smells funny.
next prev parent reply other threads:[~2026-09-07 21:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 17:17 Marc Zyngier
2026-09-07 20:21 ` Abel Vesa
2026-09-07 21:15 ` Marc Zyngier [this message]
2026-09-08 7:34 ` Abel Vesa
2026-09-08 8:29 ` Raviteja Laggyshetty
2026-09-08 10:46 ` Marc Zyngier
2026-09-08 8:42 ` Marc Zyngier
2026-09-15 12:12 ` Thorsten Leemhuis
2026-09-15 12:39 ` Marc Zyngier
2026-09-15 12:46 ` Abel Vesa
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=87ld9c4vc2.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=abel.vesa@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raviteja.laggyshetty@oss.qualcomm.com \
--cc=smostafa@google.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®