From: Peter Xu <peterx@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: marcandre.lureau@redhat.com, qemu-devel@nongnu.org,
Kevin Wolf <kwolf@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Fabiano Rosas <farosas@suse.de>, John Snow <jsnow@redhat.com>,
Hanna Reitz <hreitz@redhat.com>,
Leonardo Bras <leobras@redhat.com>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
qemu-block@nongnu.org, Jason Wang <jasowang@redhat.com>
Subject: Re: [PATCH v2 5/9] migration: check required subsections are loaded, once
Date: Tue, 24 Oct 2023 16:10:46 -0400 [thread overview]
Message-ID: <ZTgkxrbemYtW9yK7@x1n> (raw)
In-Reply-To: <875y2w1evf.fsf@secure.mitica>
On Tue, Oct 24, 2023 at 12:41:56PM +0200, Juan Quintela wrote:
> > @@ -509,6 +538,13 @@ static int vmstate_subsection_load(QEMUFile *f, const VMStateDescription *vmsd,
> > }
> > }
> >
> > + for (i = 0; i < n; i++) {
> > + if (!visited[i] && vmstate_section_needed(vmsd->subsections[i], opaque)) {
> > + trace_vmstate_subsection_load_bad(vmsd->name, vmsd->subsections[i]->name, "(not visited)");
> > + return -ENOENT;
> > + }
> > + }
> > +
> > trace_vmstate_subsection_load_good(vmsd->name);
> > return 0;
> > }
>
> This part is the only one where I can see there could be some
> discussion. So I wil wait to see what other people think.
Previous email:
https://lore.kernel.org/qemu-devel/ZR2P1RbxCfBdYBaQ@x1n/
I still think it is safer to not fail unless justified that we won't hit
surprises in the ->needed(). There are a lot so I assume it's non-trivial
to justify.
We can switch the tracepoint into error_report() in that case, though, as
long as it won't fail the migration.
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2023-10-24 20:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 8:40 [PATCH v2 0/9] RFC: migration: check required entries and sections are loaded marcandre.lureau
2023-10-24 8:40 ` [PATCH v2 1/9] block/fdc: 'phase' is not needed on load marcandre.lureau
2023-10-24 8:40 ` [PATCH v2 2/9] virtio: make endian_needed() work during loading marcandre.lureau
2023-10-24 8:40 ` [PATCH v2 3/9] net/slirp: use different IDs for each instance marcandre.lureau
2023-10-24 9:26 ` Juan Quintela
2023-10-24 8:40 ` [PATCH v2 4/9] migration: rename vmstate_save_needed->vmstate_section_needed marcandre.lureau
2023-10-24 10:35 ` Juan Quintela
2023-10-24 8:40 ` [PATCH v2 5/9] migration: check required subsections are loaded, once marcandre.lureau
2023-10-24 10:41 ` Juan Quintela
2023-10-24 20:10 ` Peter Xu [this message]
2023-10-24 8:40 ` [PATCH v2 6/9] migration: check required entries " marcandre.lureau
2023-10-24 10:44 ` Juan Quintela
2023-10-24 8:40 ` [PATCH v2 7/9] migration: set file error on subsection loading marcandre.lureau
2023-10-24 9:27 ` Juan Quintela
2023-10-24 8:40 ` [PATCH v2 8/9] test-vmstate: add some subsection tests marcandre.lureau
2023-10-24 10:45 ` Juan Quintela
2023-10-24 8:40 ` [PATCH v2 9/9] docs/migration: reflect the changes about needed subsections marcandre.lureau
2023-10-24 10:47 ` Juan Quintela
2023-10-24 10:58 ` Marc-André Lureau
2023-10-24 11:08 ` Juan Quintela
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=ZTgkxrbemYtW9yK7@x1n \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=hreitz@redhat.com \
--cc=jasowang@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=leobras@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=samuel.thibault@ens-lyon.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).