From: Jakub Kicinski <kuba@kernel.org>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>
Cc: netdev@vger.kernel.org, Stefan Hajnoczi <stefanha@redhat.com>,
Jason Wang <jasowang@redhat.com>,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>, Vilas R K <vilas.r.k@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] vsock/virtio: add support for device suspend/resume
Date: Mon, 2 May 2022 16:07:10 -0700 [thread overview]
Message-ID: <20220502160710.68381a27@kernel.org> (raw)
In-Reply-To: <20220502180554-mutt-send-email-mst@kernel.org>
On Mon, 2 May 2022 18:20:51 -0400 Michael S. Tsirkin wrote:
> On Thu, Apr 28, 2022 at 03:22:39PM +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.
> >
> > Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
>
>
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
Commit 0530a683fc85 ("Merge branch
'vsock-virtio-add-support-for-device-suspend-resume'") in net-next, now.
Thank you!
prev parent reply other threads:[~2022-05-02 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 13:22 [PATCH net-next 0/2] vsock/virtio: add support for device suspend/resume Stefano Garzarella
2022-04-28 13:22 ` [PATCH net-next 1/2] vsock/virtio: factor our the code to initialize and delete VQs Stefano Garzarella
2022-04-28 13:22 ` [PATCH net-next 2/2] vsock/virtio: add support for device suspend/resume Stefano Garzarella
2022-05-02 21:35 ` [PATCH net-next 0/2] " Jakub Kicinski
2022-05-02 22:20 ` Michael S. Tsirkin
2022-05-02 23:07 ` Jakub Kicinski [this message]
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=20220502160710.68381a27@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=vilas.r.k@intel.com \
--cc=virtualization@lists.linux-foundation.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).