On Tue, Oct 18, 2022 at 3:58 PM Boeuf, Sebastien
<sebastien.boeuf at intel.com> wrote:>
> On Tue, 2022-10-18 at 02:15 -0400, Michael S. Tsirkin wrote:
> > On Mon, Oct 17, 2022 at 02:06:19PM +0200,
> > sebastien.boeuf at intel.com wrote:
> > > From: Sebastien Boeuf <sebastien.boeuf at 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 | 19 ++++++++++++++++++
> > > 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, 67 insertions(+), 2 deletions(-)
> >
> >
> > Not on list:
> >
> > $ b4 mbox cover.1666008238.git.sebastien.boeuf at intel.com
> > Looking up
> >
https://lore.kernel.org/r/cover.1666008238.git.sebastien.boeuf%40intel.com
> > That message-id is not known.
> > $
> >
> >
> > dropped for now.
>
> Oh I didn't realize the list wasn't receiving my patch series. What
is
> the correct list? I was using virtualization at lists.linux-foundation.org
> which I found from the MAINTAINERS file.
Have you tried to use scripts/get_maintainer.pl? I guess all patches
should be copied to linux-kernel at vger.kernel.org at least.
Thanks
>
> >
> > > --
> > > 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.
> >
>
> ---------------------------------------------------------------------
> 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.