From: Juan Quintela <quintela@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: owasserm@redhat.com, shajnocz@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] arch_init/ram_load: add error message for block length mismatch
Date: Mon, 13 May 2013 10:57:57 +0200 [thread overview]
Message-ID: <87fvxrdzoq.fsf@elfo.elfo> (raw)
In-Reply-To: <1368357388-25906-1-git-send-email-alevy@redhat.com> (Alon Levy's message of "Sun, 12 May 2013 14:16:28 +0300")
Alon Levy <alevy@redhat.com> wrote:
> Makes it easier to debug situations where the source and target have
> different ram blocks in a device and migration fails due to that, for
> instance a BAR size change on a PCI device.
>
> Signed-off-by: Alon Levy <alevy@redhat.com>
> ---
> v3: use RAM_ADDR_FMT
>
> arch_init.c | 3 +++
> 1 file changed, 3 insertions(+)
>
Reviewed-by: Juan Quintela <quintela@redhat.com>
will be included in next pull request. thanks.
> diff --git a/arch_init.c b/arch_init.c
> index 49c5dc2..cd27fcf 100644
> --- a/arch_init.c
> +++ b/arch_init.c
> @@ -808,6 +808,9 @@ static int ram_load(QEMUFile *f, void *opaque, int version_id)
> QTAILQ_FOREACH(block, &ram_list.blocks, next) {
> if (!strncmp(id, block->idstr, sizeof(id))) {
> if (block->length != length) {
> + fprintf(stderr, "Length mismatch: %s: %ld "
> + "in != " RAM_ADDR_FMT "\n", id, length,
> + block->length);
> ret = -EINVAL;
> goto done;
> }
prev parent reply other threads:[~2013-05-13 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 11:16 [Qemu-devel] [PATCH v3] arch_init/ram_load: add error message for block length mismatch Alon Levy
2013-05-13 8:57 ` Juan Quintela [this message]
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=87fvxrdzoq.fsf@elfo.elfo \
--to=quintela@redhat.com \
--cc=alevy@redhat.com \
--cc=owasserm@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shajnocz@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 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.