[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v4 1/5] virtio: add "use-started" property
From: |
Yongji Xie |
Subject: |
Re: [Qemu-devel] [PATCH v4 1/5] virtio: add "use-started" property |
Date: |
Thu, 27 Jun 2019 10:20:12 +0800 |
On Wed, 26 Jun 2019 at 18:18, Greg Kurz <address@hidden> wrote:
>
> On Wed, 26 Jun 2019 10:31:26 +0800
> address@hidden wrote:
>
> > From: Xie Yongji <address@hidden>
> >
> > In order to avoid migration issues, we introduce a "use-started"
> > property to the base virtio device to indicate whether use
> > "started" flag or not. This property will be true by default and
> > set to false when machine type <= 4.0.
> >
> > Suggested-by: Greg Kurz <address@hidden>
> > Signed-off-by: Xie Yongji <address@hidden>
> > ---
>
> LGTM,
>
> Reviewed-by: Greg Kurz <address@hidden>
>
> This fixes the backward migration breakage I was observing.
>
> Tested-by: Greg Kurz <address@hidden>
>
Thanks for the testing.
- [Qemu-devel] [PATCH v4 0/5] virtio: fix some issues of "started" and "start_on_kick" flag, elohimes, 2019/06/25
- [Qemu-devel] [PATCH v4 2/5] virtio: Set "start_on_kick" for legacy devices, elohimes, 2019/06/25
- [Qemu-devel] [PATCH v4 3/5] virtio: Set "start_on_kick" on virtio_set_features(), elohimes, 2019/06/25
- [Qemu-devel] [PATCH v4 1/5] virtio: add "use-started" property, elohimes, 2019/06/25
- [Qemu-devel] [PATCH v4 5/5] virtio: Don't change "started" flag on virtio_vmstate_change(), elohimes, 2019/06/25
- [Qemu-devel] [PATCH v4 4/5] virtio: Make sure we get correct state of device on handle_aio_output(), elohimes, 2019/06/25
- Re: [Qemu-devel] [PATCH v4 0/5] virtio: fix some issues of "started" and "start_on_kick" flag, Laurent Vivier, 2019/06/26