All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Avihai Horon" <avihaih@nvidia.com>,
	"Alex Williamson" <alex.williamson@redhat.com>,
	"Fabiano Rosas" <farosas@suse.de>,
	peterx@redhat.com, "Cédric Le Goater" <clg@redhat.com>
Subject: [PATCH 0/2] Migration: Make misc.h helpers available for whole VM lifecycle
Date: Tue, 22 Oct 2024 12:07:18 -0400	[thread overview]
Message-ID: <20241022160720.1013543-1-peterx@redhat.com> (raw)

This is a follow up of below patch from Avihai as a replacement:

https://lore.kernel.org/qemu-devel/20241020130108.27148-3-avihaih@nvidia.com/

It allows all misc.h exported helpers to be used for the whole VM
lifecycle, so as to never crash QEMU with freed migration objects.

I did also add some comments explaining lock requirements for using the
helpers, which used to be ambiguous.  Hopefully that clarify things too.

Thanks,

Peter Xu (2):
  migration: Make all helpers in misc.h safe to use without migration
  migration: Unexport dirty_bitmap_mig_init() in misc.h

 include/migration/misc.h | 36 ++++++++++++++++++++++++++++--------
 migration/migration.h    |  4 ++++
 migration/migration.c    | 22 +++++++++++++++++++++-
 3 files changed, 53 insertions(+), 9 deletions(-)

-- 
2.45.0



             reply	other threads:[~2024-10-22 16:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22 16:07 Peter Xu [this message]
2024-10-22 16:07 ` [PATCH 1/2] migration: Make all helpers in misc.h safe to use without migration Peter Xu
2024-10-22 16:11   ` Cédric Le Goater
2024-10-22 21:52     ` Peter Xu
2024-10-23  8:30   ` Avihai Horon
2024-10-23 15:14     ` Peter Xu
2024-10-23 15:25       ` Peter Xu
2024-10-22 16:07 ` [PATCH 2/2] migration: Unexport dirty_bitmap_mig_init() in misc.h Peter Xu
2024-10-22 16:13   ` Cédric Le Goater

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=20241022160720.1013543-1-peterx@redhat.com \
    --to=peterx@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=avihaih@nvidia.com \
    --cc=clg@redhat.com \
    --cc=farosas@suse.de \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.