On Mon, Apr 15, 2024 at 05:11:05PM +0800, Cindy Lu wrote:
> On Mon, Apr 15, 2024 at 4:32 PM Michael S. Tsirkin wrote:
> >
> > On Fri, Apr 12, 2024 at 02:26:55PM +0800, Cindy Lu wrote:
> > > During the booting process of the non-standard image, the behavior of the
> > > called function in qemu is
On Mon, Apr 15, 2024 at 4:32 PM Michael S. Tsirkin wrote:
>
> On Fri, Apr 12, 2024 at 02:26:55PM +0800, Cindy Lu wrote:
> > During the booting process of the non-standard image, the behavior of the
> > called function in qemu is as follows:
> >
> > 1. vhost_net_stop() was triggered by guest
On Fri, Apr 12, 2024 at 02:26:55PM +0800, Cindy Lu wrote:
> During the booting process of the non-standard image, the behavior of the
> called function in qemu is as follows:
>
> 1. vhost_net_stop() was triggered by guest image. This will call the function
> virtio_pci_set_guest_notifiers() with
On Fri, Apr 12, 2024 at 2:28 PM Cindy Lu wrote:
>
> During the booting process of the non-standard image, the behavior of the
> called function in qemu is as follows:
>
> 1. vhost_net_stop() was triggered by guest image. This will call the function
> virtio_pci_set_guest_notifiers() with assgin=
QE tested this patch with regression tests, everything works fine.
Tested-by: Lei Yang
On Fri, Apr 12, 2024 at 2:37 PM Cindy Lu wrote:
>
> Hi All
> I apologize for bothering you again
> I send the new patch is because I found that the function
>
Hi All
I apologize for bothering you again
I send the new patch is because I found that the function
kvm_virtio_pci_vector_use_one/kvm_virtio_pci_vector_release_one
can only change the vector that already set to the device.
ret = virtio_pci_get_notifier(proxy, queue_no, , );
if (ret < 0)
During the booting process of the non-standard image, the behavior of the
called function in qemu is as follows:
1. vhost_net_stop() was triggered by guest image. This will call the function
virtio_pci_set_guest_notifiers() with assgin= false,
virtio_pci_set_guest_notifiers(） will release the
