From: Anders Roxell <anders.roxell@linaro•org>
To: Inochi Amaoto <inochiama@gmail•com>,
regressions@lists•linux.dev, linux-next@vger•kernel.org
Cc: Thomas Gleixner <tglx@linutronix•de>,
Bjorn Helgaas <bhelgaas@google•com>,
Marc Zyngier <maz@kernel•org>,
Lorenzo Pieralisi <lpieralisi@kernel•org>,
Shradha Gupta <shradhagupta@linux•microsoft.com>,
Haiyang Zhang <haiyangz@microsoft•com>,
Jonathan Cameron <Jonathan.Cameron@huwei•com>,
Juergen Gross <jgross@suse•com>,
Nicolin Chen <nicolinc@nvidia•com>,
Jason Gunthorpe <jgg@ziepe•ca>,
Chen Wang <unicorn_wang@outlook•com>,
linux-kernel@vger•kernel.org, linux-pci@vger•kernel.org,
Yixun Lan <dlan@gentoo•org>, Longbin Li <looong.bin@gmail•com>,
arnd@arndb•de, dan.carpenter@linaro•org,
naresh.kamboju@linaro•org, benjamin.copeland@linaro•org
Subject: Re: [PATCH v2 2/4] PCI/MSI: Add startup/shutdown for per device domains
Date: Tue, 26 Aug 2025 21:45:48 +0200 [thread overview]
Message-ID: <aK4O7Hl8NCVEMznB@monster> (raw)
In-Reply-To: <20250813232835.43458-3-inochiama@gmail.com>
On 2025-08-14 07:28, Inochi Amaoto wrote:
> As the RISC-V PLIC can not apply affinity setting without calling
> irq_enable(), it will make the interrupt unavailble when using as
> an underlying IRQ chip for MSI controller.
>
> Implement .irq_startup() and .irq_shutdown() for the PCI MSI and
> MSI-X templates. For chips that specify MSI_FLAG_PCI_MSI_STARTUP_PARENT,
> these startup and shutdown the parent as well, which allows the
> irq on the parent chip to be enabled if the irq is not enabled
> when allocating. This is necessary for the MSI controllers which
> use PLIC as underlying IRQ chip.
>
> Suggested-by: Thomas Gleixner <tglx@linutronix•de>
> Signed-off-by: Inochi Amaoto <inochiama@gmail•com>
Regressions found while booting the Linux next-20250826 on the
qemu-arm64, qemu-armv7 due to following kernel log.
Bisection identified this commit as the cause of the regression.
Regression Analysis:
- New regression? Yes
- Reproducible? Yes
First seen on the next-20250826
Good: next-20250825
Bad: next-20250826
Test regression: next-20250826 gcc-13 boot failed on qemu-arm64 and
qemu-armv7.
Expected behavior: System should boot normally and virtio block devices
should be detected and initialized immediately.
Actual behavior: System hangs for ~30 seconds during virtio block device
initialization before showing scheduler deadline replenish errors and
failing to complete boot.
Reported-by: Linux Kernel Functional Testing <lkft@linaro•org>
[...]
<6>[ 1.369038] virtio-pci 0000:00:01.0: enabling device (0000 ->
0003)
<6>[ 1.420097] Serial: 8250/16550 driver, 4 ports, IRQ sharing
enabled
<6>[ 1.450858] msm_serial: driver initialized
<6>[ 1.454489] SuperH (H)SCI(F) driver initialized
<6>[ 1.456056] STM32 USART driver initialized
<6>[ 1.513325] loop: module loaded
<6>[ 1.515744] virtio_blk virtio0: 2/0/0 default/read/poll queues
<5>[ 1.527859] virtio_blk virtio0: [vda] 5397504 512-byte logical
blocks (2.76 GB/2.57 GiB)
<4>[ 29.761219] sched: DL replenish lagged too much
[here it hangs]
Reverting this commit restores normal boot behavior.
qemu-arm64
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250826/testrun/29663822/suite/boot/test/gcc-13-lkftconfig/log
qemu-armv7
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250826/testrun/29663615/suite/boot/test/gcc-13-lkftconfig/log
## Source
* Git tree:
* https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git
* Git sha: d0630b758e593506126e8eda6c3d56097d1847c5
* Git describe: next-20250826
* Project details: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250826
* Architectures: arm64
* Toolchains: gcc-13
* Kconfigs: gcc-13-lkftconfig
## Build
* Test history: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250826/testrun/29663822/suite/boot/test/gcc-13-lkftconfig/history/
* Test link: https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/tests/31oo1cMOi0uSNKYApi80iQahbLi
* Build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/31onzS5UmJVvvZucEhtB1veoJA1/
* Kernel config: https://storage.tuxsuite.com/public/linaro/lkft/builds/31onzS5UmJVvvZucEhtB1veoJA1/config
--
Linaro LKFT
https://lkft.linaro.org
next parent reply other threads:[~2025-08-26 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250813232835.43458-1-inochiama@gmail.com>
[not found] ` <20250813232835.43458-3-inochiama@gmail.com>
2025-08-26 19:45 ` Anders Roxell [this message]
2025-08-26 22:09 ` [PATCH v2 2/4] PCI/MSI: Add startup/shutdown for per device domains Nathan Chancellor
2025-08-27 10:33 ` Mark Brown
2025-08-26 22:33 ` Inochi Amaoto
2025-08-26 23:28 ` Inochi Amaoto
2025-08-27 0:47 ` Nathan Chancellor
2025-08-27 8:17 ` Naresh Kamboju
2025-08-27 9:45 ` Inochi Amaoto
2025-08-27 9:44 ` Inochi Amaoto
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=aK4O7Hl8NCVEMznB@monster \
--to=anders.roxell@linaro$(echo .)org \
--cc=Jonathan.Cameron@huwei$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=benjamin.copeland@linaro$(echo .)org \
--cc=bhelgaas@google$(echo .)com \
--cc=dan.carpenter@linaro$(echo .)org \
--cc=dlan@gentoo$(echo .)org \
--cc=haiyangz@microsoft$(echo .)com \
--cc=inochiama@gmail$(echo .)com \
--cc=jgg@ziepe$(echo .)ca \
--cc=jgross@suse$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-pci@vger$(echo .)kernel.org \
--cc=looong.bin@gmail$(echo .)com \
--cc=lpieralisi@kernel$(echo .)org \
--cc=maz@kernel$(echo .)org \
--cc=naresh.kamboju@linaro$(echo .)org \
--cc=nicolinc@nvidia$(echo .)com \
--cc=regressions@lists$(echo .)linux.dev \
--cc=shradhagupta@linux$(echo .)microsoft.com \
--cc=tglx@linutronix$(echo .)de \
--cc=unicorn_wang@outlook$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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