[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aNvzKq7itcc3ZY_Y@google.com>
Date: Tue, 30 Sep 2025 08:11:38 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: "open list:KERNEL SELFTEST FRAMEWORK" <linux-kselftest@...r.kernel.org>, kvmarm@...ts.linux.dev,
open list <linux-kernel@...r.kernel.org>, lkft-triage@...ts.linaro.org,
Linux Regressions <regressions@...ts.linux.dev>, kvm list <kvm@...r.kernel.org>,
Paolo Bonzini <pbonzini@...hat.com>, K Prateek Nayak <kprateek.nayak@....com>,
Arnd Bergmann <arnd@...db.de>, Dan Carpenter <dan.carpenter@...aro.org>,
Anders Roxell <anders.roxell@...aro.org>, Ben Copeland <benjamin.copeland@...aro.org>
Subject: Re: selftests: kvm: irqfd_test: KVM_IRQFD failed, rc: -1 errno: 11
(Resource temporarily unavailable)
On Tue, Sep 30, 2025, Naresh Kamboju wrote:
> The selftests: kvm: irqfd_test consistently fails across all test platforms
> since its introduction in Linux next-20250625. The failure occurs due to
> a KVM_IRQFD ioctl returning errno 11 (Resource temporarily unavailable).
> This has been observed from day one and is reproducible on all test runs.
It's a known issue[*], that I think we kinda forgot about. The underlying issue
is that KVM ARM needs the test to create a vGIC, but the fix stalled out a bit
because there isn't one single, "obviously correct" way to do that.
I'll Cc you and ping Oliver on the other thread.
[*] https://lore.kernel.org/all/20250825155203.71989-1-sebott@redhat.com
Powered by blists - more mailing lists