public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: sebastien.boeuf@intel.com
To: linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org
Cc: mst@redhat.com, jasowang@redhat.com, eperezma@redhat.com,
	sebastien.boeuf@intel.com
Subject: [PATCH v4 0/4] vdpa: Add resume operation
Date: Tue, 18 Oct 2022 10:37:23 +0200	[thread overview]
Message-ID: <cover.1666082013.git.sebastien.boeuf@intel.com> (raw)

From: Sebastien Boeuf <sebastien.boeuf@intel.com>

This series introduces a new operation for vdpa devices. It allows them
to be resumed after they have been suspended. A new feature bit is
introduced for devices to advertise their ability to be resumed after
they have been suspended. This feature bit is different from the one
advertising the ability to be suspended, meaning a device that can be
suspended might not have the ability to be resumed.

Even if it is already possible to restore a device that has been
suspended, which is very convenient for live migrating virtual machines,
there is a major drawback as the device must be fully reset. There is no
way to resume a device that has been suspended without having to
configure the device again and without having to recreate the IOMMU
mappings. This new operation aims at filling this gap by allowing the
device to resume processing the virtqueue descriptors without having to
reset it. This is particularly useful for performing virtual machine
offline migration, also called snapshot/restore, as it allows a virtual
machine to resume to a running state after it was paused and a snapshot
of the entire system was taken.

Sebastien Boeuf (4):
  vdpa: Add resume operation
  vhost-vdpa: Introduce RESUME backend feature bit
  vhost-vdpa: uAPI to resume the device
  vdpa_sim: Implement resume vdpa op

 drivers/vdpa/vdpa_sim/vdpa_sim.c | 14 +++++++++++++
 drivers/vhost/vdpa.c             | 34 +++++++++++++++++++++++++++++++-
 include/linux/vdpa.h             |  6 +++++-
 include/uapi/linux/vhost.h       |  8 ++++++++
 include/uapi/linux/vhost_types.h |  2 ++
 5 files changed, 62 insertions(+), 2 deletions(-)

-- 
2.34.1

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 5 208 026.16 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


             reply	other threads:[~2022-10-18  8:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  8:37 sebastien.boeuf [this message]
2022-10-18  8:37 ` [PATCH v4 1/4] vdpa: Add resume operation sebastien.boeuf
2022-10-18  8:37 ` [PATCH v4 2/4] vhost-vdpa: Introduce RESUME backend feature bit sebastien.boeuf
2022-10-18  8:37 ` [PATCH v4 3/4] vhost-vdpa: uAPI to resume the device sebastien.boeuf
2022-10-18  8:37 ` [PATCH v4 4/4] vdpa_sim: Implement resume vdpa op sebastien.boeuf
2022-10-18 10:53   ` kernel test robot
2022-10-19  9:31   ` Eugenio Perez Martin
2022-10-19  9:37     ` Boeuf, Sebastien

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=cover.1666082013.git.sebastien.boeuf@intel.com \
    --to=sebastien.boeuf@intel.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.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