From: William McVicker <willmcvicker@google.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Alim Akhtar <alim.akhtar@samsung.com>,
Ingo Molnar <mingo@kernel.org>,
Peter Griffin <peter.griffin@linaro.org>,
Youngmin Nam <youngmin.nam@samsung.com>
Subject: Re: [PATCH] clocksource/drivers/exynos_mct: Use percpu interrupts only on ARM64
Date: Wed, 24 Sep 2025 17:17:39 +0000 [thread overview]
Message-ID: <aNQnszeIfeHjx3GS@google.com> (raw)
In-Reply-To: <6a89a8bf-022d-4c31-b6db-95763142e603@linaro.org>
Hi Daniel,
On 09/24/2025, Daniel Lezcano wrote:
>
> Hi Marek,
>
> On 19/09/2025 23:31, Marek Szyprowski wrote:
> > On 27.08.2025 13:58, Krzysztof Kozlowski wrote:
> > > On 27/08/2025 12:26, Marek Szyprowski wrote:
> > > > For some unknown reasons forcing percpu interrupts for local timers
> > > > breaks CPU hotplug for 'little' cores on legacy ARM 32bit Exynos based
> > > > machines (for example Exynos5422-based Odroid-XU3/XU4 boards). Use percpu
> > > > flag only when driver is compiled for newer ARM64 architecture.
> > > >
> > > > Fixes: f3cec54ee3bf ("clocksource/drivers/exynos_mct: Set local timer interrupts as percpu")
> > >
> > > I am pretty sure the patch above was not tested on arm32, thus this
> > > workaround seems reasonable.
> > >
> > > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> >
> > Daniel, any chance to get this merged?
>
> The patch does not apply. However it is not your fault but a glitch in the
> previous pull request and the regression found in the Exynos MCT.
>
> Apparently, Thomas had to drop the entire pull request while I thought he
> dropped only Will's changes.
>
> A pull request with the previous changes for v6.17-rc1 and with the new
> changes for v6.18-rc1 is about to be emitted but without the Exynos MCT
> changes for the modularization. That means your change does not apply
> correctly anymore on the current changes.
Is there somewhere I can check to see which changes will be re-sent? I don't
see them in the timers/drivers/next branch. Will it be patches 2-4 plus the
fixes for the section mismatch and this new IRQ fix? Once that's all sorted
out, I'll base the new modularization patches on top of that.
Thanks,
Will
next prev parent reply other threads:[~2025-09-24 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250827102650eucas1p1fe270adbf29c649b9ce529e1d45aabc3@eucas1p1.samsung.com>
2025-08-27 10:26 ` [PATCH] clocksource/drivers/exynos_mct: Use percpu interrupts only on ARM64 Marek Szyprowski
2025-08-27 11:58 ` Krzysztof Kozlowski
2025-09-19 21:31 ` Marek Szyprowski
2025-09-24 8:41 ` Daniel Lezcano
2025-09-24 8:53 ` Marek Szyprowski
2025-09-24 17:17 ` William McVicker [this message]
2025-09-25 6:37 ` Marek Szyprowski
2025-09-25 8:07 ` Daniel Lezcano
2025-09-23 10:09 ` Peter Griffin
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=aNQnszeIfeHjx3GS@google.com \
--to=willmcvicker@google.com \
--cc=alim.akhtar@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mingo@kernel.org \
--cc=peter.griffin@linaro.org \
--cc=tglx@linutronix.de \
--cc=youngmin.nam@samsung.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;
as well as URLs for NNTP newsgroup(s).