From: Jason Wang <jasowang@redhat.com>
To: Cindy Lu <lulu@redhat.com>
Cc: mst@redhat.com, qemu-devel@nongnu.org
Subject: Re: [RFC 0/2] disable the configuration interrupt for the unsupported device
Date: Wed, 27 Mar 2024 11:05:05 +0800 [thread overview]
Message-ID: <CACGkMEt5fTtwmeb18Yj0xDT_bCjsJQM2nB-u1GJDfFKnEtSSHA@mail.gmail.com> (raw)
In-Reply-To: <20240327012905.70188-1-lulu@redhat.com>
Hi Cindy:
On Wed, Mar 27, 2024 at 9:29 AM Cindy Lu <lulu@redhat.com> wrote:
>
> we need a crash in Non-standard image, here is the jira for this https://issues.redhat.com/browse/RHEL-28522
> The root cause of the issue is that an IRQFD was used without initialization..
>
> During the booting process of the Vyatta image, the behavior of the called function in qemu is as follows:
>
> 1. vhost_net_stop() was called, this will call the function
> virtio_pci_set_guest_notifiers() with assgin= false, and
> virtio_pci_set_guest_notifiers() will release the irqfd for vector 0
Before vhost_net_stop(), do we know which vector is used by which queue?
>
> 2. virtio_reset() was called -->set configure vector to VIRTIO_NO_VECTORt
>
> 3.vhost_net_start() was called (at this time the configure vector is
> still VIRTIO_NO_VECTOR) and call virtio_pci_set_guest_notifiers() with
> assgin= true, so the irqfd for vector 0 was not "init" during this process
How does the configure vector differ from the virtqueue vector here?
>
> 4. The system continues to boot and msix_fire_vector_notifier() was
> called unmask the vector 0 and then met the crash
> [msix_fire_vector_notifier] 112 called vector 0 is_masked 1
> [msix_fire_vector_notifier] 112 called vector 0 is_masked 0
>
> The reason for not reproducing in RHEL/fedora guest image is because
> REHL/Fedora doesn't have the behavior of calling vhost_net_stop and then virtio_reset, and also won't call msix_fire_vector_notifier for vector 0 during system boot.
>
> The reason for not reproducing before configure interrupt support is because
> vector 0 is for configure interrupt, before the support for configure interrupts, the notifier process will not handle vector 0.
>
> For the device Vyatta using, it doesn't support configure interrupts at all, So we plan to disable the configure interrupts in unsupported device
Btw, let's tweak the changelog, it's a little bit hard to understand.
Thanks
>
> Signed-off-by: Cindy Lu <lulu@redhat.com>
>
> Cindy Lu (2):
> virtio-net: disable the configure interrupt for not support device
> virtio-pci: check if the configure interrupt enable
>
> hw/net/virtio-net.c | 5 ++++-
> hw/virtio/virtio-pci.c | 41 +++++++++++++++++++++-----------------
> hw/virtio/virtio.c | 1 +
> include/hw/virtio/virtio.h | 1 +
> 4 files changed, 29 insertions(+), 19 deletions(-)
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-03-27 3:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 1:22 [RFC 0/2] disable the configuration interrupt for the unsupported device Cindy Lu
2024-03-27 1:22 ` [RFC 1/2] virtio-net: disable the configure interrupt for not support device Cindy Lu
2024-03-27 2:54 ` Jason Wang
2024-03-27 1:22 ` [RFC 2/2] virtio-pci: check if the configure interrupt enable Cindy Lu
2024-03-27 3:05 ` Jason Wang [this message]
2024-03-27 6:02 ` [RFC 0/2] disable the configuration interrupt for the unsupported device Cindy Lu
2024-03-27 7:54 ` Jason Wang
2024-03-27 8:28 ` Cindy Lu
2024-03-27 9:12 ` Jason Wang
2024-03-27 9:12 ` Jason Wang
2024-03-27 9:43 ` Cindy Lu
2024-03-28 4:14 ` Jason Wang
2024-03-28 7:07 ` Cindy Lu
2024-03-27 9:32 ` Cindy Lu
2024-03-28 4:12 ` Jason Wang
2024-03-29 3:02 ` Cindy Lu
2024-03-29 3:27 ` Jason Wang
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=CACGkMEt5fTtwmeb18Yj0xDT_bCjsJQM2nB-u1GJDfFKnEtSSHA@mail.gmail.com \
--to=jasowang@redhat.com \
--cc=lulu@redhat.com \
--cc=mst@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).