From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Marc Zyngier <maz@kernel.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
'Linux Samsung SOC' <linux-samsung-soc@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
John Garry <john.garry@huawei.com>,
Xiongfeng Wang <wangxiongfeng2@huawei.com>,
David Decotigny <ddecotig@google.com>
Subject: Re: [PATCH v3 2/3] genirq: Always limit the affinity to online CPUs
Date: Wed, 20 Apr 2022 11:47:22 +0200 [thread overview]
Message-ID: <9e2306a9-8181-ba43-e331-b3b70c1a72eb@samsung.com> (raw)
In-Reply-To: <70123e98-046f-f10e-1032-8d112edd3ecf@linaro.org>
Hi Krzysztof,
On 20.04.2022 11:13, Krzysztof Kozlowski wrote:
> On 14/04/2022 13:08, Marek Szyprowski wrote:
>>> Thanks for all of the debug, super helpful. The issue is that we don't
>>> handle the 'force' case, which a handful of drivers are using when
>>> bringing up CPUs (and doing so before the CPUs are marked online).
>>>
>>> Can you please give the below hack a go?
>> This patch fixed the issue. Thanks! Feel free to add my:
>>
>> Reported-by: Marek Szyprowski <m.szyprowski@samsung.com>
>>
>> Tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
> Hi Marc,
>
> Linux-next still fails to boot on Exynos5422 boards, so I wonder if you
> applied the fix?
>
> Instead of silent fail there is now "Unable to handle kernel paging
> request at virtual address f0836644", so it is slightly different.
This is yet another issue (related to all ARM 32bit boards) introduced
in next-20220413, see:
https://lore.kernel.org/all/20220405014836.14077-1-peterx@redhat.com/T/#m6137721ae1323fdf424cee0f8ea1a6af5a3af396
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
next prev parent reply other threads:[~2022-04-20 9:47 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
[not found] ` <CGME20220413145922eucas1p2dc46908354f4d2b48db79978d086a838@eucas1p2.samsung.com>
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 [this message]
2022-04-20 9:50 ` Krzysztof Kozlowski
2022-04-14 10:49 ` Thomas Gleixner
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=9e2306a9-8181-ba43-e331-b3b70c1a72eb@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=ddecotig@google.com \
--cc=john.garry@huawei.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=maz@kernel.org \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®