From: "Michael S. Tsirkin" <mst@redhat.com>
To: Andrew Stellman <astellman@stellman-greene.com>
Cc: "Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
virtualization@lists.linux.dev
Subject: Re: [PATCH 3/4] virtio-pci: return IRQ_HANDLED for config-change interrupts
Date: Tue, 7 Apr 2026 16:53:44 -0400 [thread overview]
Message-ID: <20260407165323-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAChPuV9iGu6o5yJz87DEo6=gfr2P7m_jM=-auFuZevrr-HoYNw@mail.gmail.com>
On Tue, Apr 07, 2026 at 01:35:26PM -0400, Andrew Stellman wrote:
> Fixes: 77cf524654a8 ("virtio_pci: split up vp_interrupt")
>
> Should I resend as v2 with the tag included, or is adding it on your end
> easier?
how was this tested? I don't think a unit test is sufficient here, FYI.
> On Tue, Apr 7, 2026 at 12:20 PM Michael S. Tsirkin <mst@redhat.com> wrote:
>
> On Tue, Apr 07, 2026 at 08:39:03AM -0400, Andrew Stellman wrote:
> > vp_interrupt() unconditionally returns the result of
> > vp_vring_interrupt(). When a config-change interrupt fires but no vring
> > activity is pending, vp_vring_interrupt() returns IRQ_NONE — even
> > though the interrupt was legitimately handled by vp_config_changed().
> > Over time this causes the IRQ subsystem to flag the line as spurious.
> >
> > Track the return value explicitly: set ret to IRQ_HANDLED when the
> > config-change bit is set, OR it with the vring result, and return the
> > combined value.
> >
> > Signed-off-by: Andrew Stellman <astellman@stellman-greene.com>
>
> Fixes tag?
>
> > ---
> > drivers/virtio/virtio_pci_common.c | 10 ++++++++--
> > 1 file changed, 8 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/virtio/virtio_pci_common.c b/drivers/virtio/
> virtio_pci_common.c
> > index 0b9d66b..1d1ab02 100644
> > --- a/drivers/virtio/virtio_pci_common.c
> > +++ b/drivers/virtio/virtio_pci_common.c
> > @@ -106,6 +106,7 @@ static irqreturn_t vp_vring_interrupt(int irq, void
> *opaque)
> > static irqreturn_t vp_interrupt(int irq, void *opaque)
> > {
> > struct virtio_pci_device *vp_dev = opaque;
> > + irqreturn_t ret = IRQ_NONE;
> > u8 isr;
> >
> > /* reading the ISR has the effect of also clearing it so it's very
> > @@ -117,10 +118,15 @@ static irqreturn_t vp_interrupt(int irq, void
> *opaque)
> > return IRQ_NONE;
> >
> > /* Configuration change? Tell driver if it wants to know. */
> > - if (isr & VIRTIO_PCI_ISR_CONFIG)
> > + if (isr & VIRTIO_PCI_ISR_CONFIG) {
> > vp_config_changed(irq, opaque);
> > + ret = IRQ_HANDLED;
> > + }
> >
> > - return vp_vring_interrupt(irq, opaque);
> > + if (vp_vring_interrupt(irq, opaque) == IRQ_HANDLED)
> > + ret = IRQ_HANDLED;
> > +
> > + return ret;
> > }
> >
> > static int vp_request_msix_vectors(struct virtio_device *vdev, int
> nvectors,
> > --
> > 2.34.1
>
>
next prev parent reply other threads:[~2026-04-07 20:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 12:39 [PATCH 0/4] virtio: fix four bugs across mmio, pci, and vring Andrew Stellman
2026-04-07 12:39 ` [PATCH 1/4] virtio-mmio: wait for status readback after reset Andrew Stellman
2026-04-07 16:24 ` Michael S. Tsirkin
2026-04-07 12:39 ` [PATCH 2/4] virtio-pci: use avq->vq_index for admin VQ in INTx path Andrew Stellman
2026-04-07 16:26 ` Michael S. Tsirkin
[not found] ` <CAChPuV9OuQw_F5dsna4meVxV6Hicxe4+674xoSx+KEev6JEEQw@mail.gmail.com>
2026-04-07 18:08 ` Michael S. Tsirkin
2026-04-07 12:39 ` [PATCH 3/4] virtio-pci: return IRQ_HANDLED for config-change interrupts Andrew Stellman
2026-04-07 16:20 ` Michael S. Tsirkin
[not found] ` <CAChPuV9iGu6o5yJz87DEo6=gfr2P7m_jM=-auFuZevrr-HoYNw@mail.gmail.com>
2026-04-07 20:53 ` Michael S. Tsirkin [this message]
2026-04-07 12:39 ` [PATCH 4/4] virtio_ring: preserve VIRTIO_F_RING_RESET in transport features Andrew Stellman
2026-04-07 16:21 ` Michael S. Tsirkin
[not found] ` <CAChPuV92aD4BibJiGfMASQVQBHAoz+3OgzQS6Hb2Dw7JDcRJTQ@mail.gmail.com>
2026-04-07 18:08 ` Michael S. Tsirkin
2026-04-07 20:00 ` Andrew Stellman
2026-04-07 20:53 ` Michael S. Tsirkin
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=20260407165323-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=astellman@stellman-greene.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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