From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Cédric Le Goater" <clg@redhat.com>, qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Magnus Kulke <magnuskulke@linux.microsoft.com>
Subject: Re: [PATCH] hw/intc/ioapic: Fix ACCEL_KERNEL_GSI_IRQFD_POSSIBLE typo
Date: Tue, 18 Nov 2025 12:27:35 +0100 [thread overview]
Message-ID: <4b153b0e-0a97-49ae-a951-0322aa9ab32c@linaro.org> (raw)
In-Reply-To: <20251106105148.737093-1-clg@redhat.com>
On 6/11/25 11:51, Cédric Le Goater wrote:
> Commit 638ac1c78457 introduced a regression in interrupt remapping
> when running a VM configured with an intel-iommu device and an
> assigned PCI VF. During boot, Linux reports repeated messages :
>
> [ 15.416794] __common_interrupt: 2.37 No irq handler for vector
> [ 15.417266] __common_interrupt: 2.37 No irq handler for vector
> [ 15.417733] __common_interrupt: 2.37 No irq handler for vector
> [ 15.418202] __common_interrupt: 2.37 No irq handler for vector
> [ 15.418670] __common_interrupt: 2.37 No irq handler for vector
>
> and may eventually hang.
>
> The issue is caused by the incorrect use of the macro
> ACCEL_KERNEL_GSI_IRQFD_POSSIBLE, which should instead be
> ACCEL_GSI_IRQFD_POSSIBLE.
>
> Fixes: 638ac1c78457 ("hw/intc: Generalize APIC helper names from kvm_* to accel_*")
> Cc: Magnus Kulke <magnuskulke@linux.microsoft.com>
> Signed-off-by: Cédric Le Goater <clg@redhat.com>
> ---
> hw/intc/ioapic.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
prev parent reply other threads:[~2025-11-18 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 10:51 [PATCH] hw/intc/ioapic: Fix ACCEL_KERNEL_GSI_IRQFD_POSSIBLE typo Cédric Le Goater
2025-11-18 11:27 ` Philippe Mathieu-Daudé [this message]
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=4b153b0e-0a97-49ae-a951-0322aa9ab32c@linaro.org \
--to=philmd@linaro.org \
--cc=clg@redhat.com \
--cc=magnuskulke@linux.microsoft.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).