From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Boeuf, Sebastien" <sebastien.boeuf@intel.com>
Cc: "eperezma@redhat.com" <eperezma@redhat.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 2/4] vhost-vdpa: Introduce RESUME backend feature bit
Date: Fri, 14 Oct 2022 10:19:15 -0400 [thread overview]
Message-ID: <20221014101858-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <129e9d73551e53c3704a1dcdb3626c0e712eed99.camel@intel.com>
On Fri, Oct 14, 2022 at 09:48:57AM +0000, Boeuf, Sebastien wrote:
> Ok thanks for the clarification. So I can remove this piece of
> validation from the code, and ultimately, each backend implementation
> could decide to complain (or not) if the userspace calls resume() when
> suspend() isn't supported. Is that a fair summary?
that's my opinion, yes.
--
MST
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
prev parent reply other threads:[~2022-10-14 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1665674878.git.sebastien.boeuf@intel.com>
[not found] ` <72bdc9ae91ca4ed8a2c9ea2aab53f8e04d4512f6.1665674878.git.sebastien.boeuf@intel.com>
2022-10-14 5:58 ` [PATCH 2/4] vhost-vdpa: Introduce RESUME backend feature bit Jason Wang
2022-10-14 6:05 ` Michael S. Tsirkin
2022-10-14 6:09 ` Jason Wang
2022-10-14 6:11 ` Michael S. Tsirkin
[not found] ` <14fc89d250788d7bdbd6b522197efc2c19ff6db8.camel@intel.com>
2022-10-14 9:37 ` Michael S. Tsirkin
[not found] ` <fb0d70a095a26a8f8adf4d7659787596d2763ef6.camel@intel.com>
2022-10-14 9:42 ` Michael S. Tsirkin
[not found] ` <129e9d73551e53c3704a1dcdb3626c0e712eed99.camel@intel.com>
2022-10-14 14:19 ` Michael S. Tsirkin [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=20221014101858-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eperezma@redhat.com \
--cc=sebastien.boeuf@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).