From: Thomas Gleixner <tglx@linutronix.de>
To: Marc Zyngier <maz@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
'Linux Samsung SOC' <linux-samsung-soc@vger.kernel.org>,
John Garry <john.garry@huawei.com>,
Xiongfeng Wang <wangxiongfeng2@huawei.com>,
David Decotigny <ddecotig@google.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH v3 2/3] genirq: Always limit the affinity to online CPUs
Date: Thu, 14 Apr 2022 12:49:38 +0200 [thread overview]
Message-ID: <87mtgodjnh.ffs@tglx> (raw)
In-Reply-To: <878rs8c2t2.wl-maz@kernel.org>
On Wed, Apr 13 2022 at 18:26, Marc Zyngier wrote:
> Marek Szyprowski <m.szyprowski@samsung.com> wrote:
>> This patch landed in linux next-20220413 as commit 33de0aa4bae9
>> ("genirq: Always limit the affinity to online CPUs"). Unfortunately it
>> breaks booting of most ARM 32bit Samsung Exynos based boards.
>>
>> I don't see anything specific in the log, though. Booting just hangs at
>> some point. The only Samsung Exynos boards that boot properly are those
>> Exynos4412 based.
>>
>> I assume that this is related to the Multi Core Timer IRQ configuration
>> specific for that SoCs. Exynos4412 uses PPI interrupts, while all other
>> Exynos SoCs have separate IRQ lines for each CPU.
>
> Can you also check that with the patch applied, it is this path that
> is taken and that it is the timer interrupts that get rejected? If
> that's the case, can you put a dump_stack() here and give me that
> stack trace? The use of irq_force_affinity() in the driver looks
> suspicious...
It's pretty clear what happens.
secondary_start_kernel()
notify_cpu_starting(cpu);
exynos4_mct_starting_cpu()
irq_force_affinity() -> fail
set_cpu_online(cpu, true);
Thanks,
tglx
next prev parent reply other threads:[~2022-04-14 10:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 18:50 [PATCH v3 0/3] genirq: Managed affinity fixes Marc Zyngier
2022-04-05 18:50 ` [PATCH v3 1/3] genirq/msi: Shutdown managed interrupts with unsatifiable affinities Marc Zyngier
2022-04-10 19:13 ` [tip: irq/core] " tip-bot2 for Marc Zyngier
2022-04-05 18:50 ` [PATCH v3 2/3] genirq: Always limit the affinity to online CPUs Marc Zyngier
2022-04-10 19:12 ` [tip: irq/core] " tip-bot2 for Marc Zyngier
2022-04-13 14:59 ` [PATCH v3 2/3] " Marek Szyprowski
2022-04-13 17:26 ` Marc Zyngier
2022-04-14 9:09 ` Marek Szyprowski
2022-04-14 10:35 ` Marc Zyngier
2022-04-14 11:08 ` Marek Szyprowski
2022-04-20 9:13 ` Krzysztof Kozlowski
2022-04-20 9:40 ` Marc Zyngier
2022-04-20 9:42 ` Krzysztof Kozlowski
2022-04-20 9:47 ` Marek Szyprowski
2022-04-20 9:50 ` Krzysztof Kozlowski
2022-04-14 10:49 ` Thomas Gleixner [this message]
2022-04-14 14:14 ` [tip: irq/core] genirq: Take the proposed affinity at face value if force==true tip-bot2 for Marc Zyngier
2022-04-05 18:50 ` [PATCH v3 3/3] irqchip/gic-v3: Always trust the managed affinity provided by the core code Marc Zyngier
2022-04-10 19:12 ` [tip: irq/core] " tip-bot2 for Marc Zyngier
2022-04-07 17:29 ` [PATCH v3 0/3] genirq: Managed affinity fixes John Garry
2022-04-08 1:02 ` Xiongfeng Wang
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=87mtgodjnh.ffs@tglx \
--to=tglx@linutronix.de \
--cc=ddecotig@google.com \
--cc=john.garry@huawei.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=maz@kernel.org \
--cc=wangxiongfeng2@huawei.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