[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220502143522.2ea422c9@kernel.org>
Date: Mon, 2 May 2022 14:35:22 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Stefano Garzarella <sgarzare@...hat.com>
Cc: netdev@...r.kernel.org, Stefan Hajnoczi <stefanha@...hat.com>,
Jason Wang <jasowang@...hat.com>, kvm@...r.kernel.org,
virtualization@...ts.linux-foundation.org,
"David S. Miller" <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>,
Vilas R K <vilas.r.k@...el.com>,
linux-kernel@...r.kernel.org, "Michael S. Tsirkin" <mst@...hat.com>
Subject: Re: [PATCH net-next 0/2] vsock/virtio: add support for device
suspend/resume
On Thu, 28 Apr 2022 15:22:39 +0200 Stefano Garzarella wrote:
> Vilas reported that virtio-vsock no longer worked properly after
> suspend/resume (echo mem >/sys/power/state).
> It was impossible to connect to the host and vice versa.
>
> Indeed, the support has never been implemented.
>
> This series implement .freeze and .restore callbacks of struct virtio_driver
> to support device suspend/resume.
>
> The first patch factors our the code to initialize and delete VQs.
> The second patch uses that code to support device suspend/resume.
This set got a "Not Applicable" in patchwork, I'm not sure why.
Michael I presume net-next is fine? Can we get an Ack?
Powered by blists - more mailing lists