qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	 Juan Quintela <quintela@redhat.com>
Subject: error reporting from pre_load etc callbacks
Date: Tue, 21 Jul 2020 15:01:28 +0100	[thread overview]
Message-ID: <CAFEAcA_rFLk2Fs1ibHH7YnR38K-nGjKas5SkPP8ReubHfHtvMQ@mail.gmail.com> (raw)

(This was pointed out to me off-list.)

What is the intended API of the pre_load() etc callbacks?
docs/devel/migration.rst doesn't say, and there's no doc comment
in include/migration/vmstate.h. Most actual device implementations
of the hooks seem to return 0 on success and -1 on failure.
But the callers of the hooks like vmstate_load_state() seem to
assume they return negative-errnos: a non-zero return value
is just propagated up to the caller, and can end up for
instance treated as negative-errno in process_incoming_migration_co():
        error_report("load of migration failed: %s", strerror(-ret));
which results in nonsensical error messages to the user like:
 qemu-system-aarch64: load of migration failed: Operation not permitted


More generally, it would be nice if a pre_load/post_load/etc
hook could report an error more precisely than just yes/no
or even than just an errno: in the case of arm CPU loading
we could in theory report more detail like which register the
kernel didn't handle...

thanks
-- PMM


             reply	other threads:[~2020-07-21 14:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 14:01 Peter Maydell [this message]
2020-07-21 14:58 ` error reporting from pre_load etc callbacks Dr. David Alan Gilbert

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=CAFEAcA_rFLk2Fs1ibHH7YnR38K-nGjKas5SkPP8ReubHfHtvMQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).