From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: [PATCH 0/2] Put Canary End of List in VMSTATE
Date: Mon, 28 Nov 2022 14:08:49 +0100 [thread overview]
Message-ID: <20221128130851.14362-1-quintela@redhat.com> (raw)
Hi
This are a patch series from David from January.
The changes that I did:
- rebases
- change assert() in vmstate_check() to and if and printf.
Please, Review.
Dr. David Alan Gilbert (2):
migration: Add canary to VMSTATE_END_OF_LIST
migration: Perform vmsd structure check during tests
include/migration/vmstate.h | 7 +++++-
migration/savevm.c | 43 +++++++++++++++++++++++++++++++++++++
migration/vmstate.c | 2 ++
3 files changed, 51 insertions(+), 1 deletion(-)
--
2.38.1
next reply other threads:[~2022-11-28 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 13:08 Juan Quintela [this message]
2022-11-28 13:08 ` [PATCH 1/2] migration: Add canary to VMSTATE_END_OF_LIST Juan Quintela
2022-11-28 13:08 ` [PATCH 2/2] migration: Perform vmsd structure check during tests Juan Quintela
2022-11-28 13:38 ` Peter Maydell
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=20221128130851.14362-1-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--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 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).