linux-kernel - Re: [patch V4 05/21] irqchip/gic-v3-its: Provide MSI parent for PCI/MSI[-X]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87h6dcxhy0.ffs@tglx>
Date: Sat, 29 Jun 2024 10:37:59 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Catalin Marinas <catalin.marinas@....com>
Cc: LKML <linux-kernel@...r.kernel.org>,
 linux-arm-kernel@...ts.infradead.org, linux-pci@...r.kernel.org,
 maz@...nel.org, anna-maria@...utronix.de, shawnguo@...nel.org,
 s.hauer@...gutronix.de, festevam@...il.com, bhelgaas@...gle.com,
 rdunlap@...radead.org, vidyas@...dia.com, ilpo.jarvinen@...ux.intel.com,
 apatel@...tanamicro.com, kevin.tian@...el.com, nipun.gupta@....com,
 den@...inux.co.jp, andrew@...n.ch, gregory.clement@...tlin.com,
 sebastian.hesselbarth@...il.com, gregkh@...uxfoundation.org,
 rafael@...nel.org, alex.williamson@...hat.com, will@...nel.org,
 lorenzo.pieralisi@....com, jgg@...lanox.com, ammarfaizi2@...weeb.org,
 robin.murphy@....com, lpieralisi@...nel.org, nm@...com, kristo@...nel.org,
 vkoul@...nel.org, okaya@...nel.org, agross@...nel.org,
 andersson@...nel.org, mark.rutland@....com,
 shameerali.kolothum.thodi@...wei.com, yuzenghui@...wei.com,
 shivamurthy.shastri@...utronix.de
Subject: Re: [patch V4 05/21] irqchip/gic-v3-its: Provide MSI parent for
 PCI/MSI[-X]

On Fri, Jun 28 2024 at 23:24, Catalin Marinas wrote:
> I just noticed guests (under KVM) failing to boot on my TX2 with your
> latest branch. I bisected to this patch as the first bad commit.
>
> I'm away this weekend, so won't have time to dive deeper. It looks like
> the CPU is stuck in do_idle() (no timer interrupts?). Also sysrq did not
> seem able to get the stack trace on the other CPUs. It fails both with a
> single or multiple CPUs in the same way place (shortly before mounting
> the rootfs and starting user space).

>From the RH log it's clear that PCI interrupts are not delivered.

> I'll drop your branch from the arm64 for-kernelci for now and have a
> look again on Monday.

I stare too. Unfortunately I don't have access to such hardware :(

Thanks,

        Thomas