qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Bharata B Rao <bharata@linux.vnet.ibm.com>
Cc: aik@ozlabs.ru, qemu-ppc@nongnu.org, qemu-devel@nongnu.org, agraf@suse.de
Subject: Re: [Qemu-devel] [RFC PATCH] spapr: Provide an error message when migration fails due to htab_shift mismatch
Date: Fri, 31 Jul 2015 17:13:11 +1000	[thread overview]
Message-ID: <20150731071311.GB15727@voom.fritz.box> (raw)
In-Reply-To: <1438268115-25273-1-git-send-email-bharata@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]

On Thu, Jul 30, 2015 at 08:25:15PM +0530, Bharata B Rao wrote:
> Include an error message when migration fails due to mismatch in
> htab_shift values at source and target. This should provide a bit more
> verbose message in addition to the current migration failure message
> that reads like:
> 
> qemu-system-ppc64: error while loading state for instance 0x0 of device 'spapr/htab'
> 
> After this patch, the failure message will look like this:
> 
> qemu-system-ppc64: htab_shift mismatch: source 29 target 24
> qemu-system-ppc64: error while loading state for instance 0x0 of device 'spapr/htab'
> 
> Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>

I've applied this to spapr-next and a new spapr-fix tree (intended for
fixes which should go to the current feature-frozen qemu, not just the
next one).  It's certainly better than the current cryptic failure.

Longer term I think we need to work harder to try to get the hash
table size the same at both ends though - we should rearrange things
so we get the size from the migration stream and then use that to feed
the hint to the kernel allocation.

Sorry I haven't looked properly yet at the patch you sent which works
towards that.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-07-31  7:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30 14:55 [Qemu-devel] [RFC PATCH] spapr: Provide an error message when migration fails due to htab_shift mismatch Bharata B Rao
2015-07-31  7:13 ` David Gibson [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=20150731071311.GB15727@voom.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).