From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: "Andreas Färber" <afaerber@suse.de>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-ppc: Add @cpu_dt_id into migration stream
Date: Thu, 27 Mar 2014 23:49:05 +1100 [thread overview]
Message-ID: <53341E41.7050101@ozlabs.ru> (raw)
In-Reply-To: <53341B8F.7040904@suse.de>
On 03/27/2014 11:37 PM, Andreas Färber wrote:
> Am 27.03.2014 03:41, schrieb Alexey Kardashevskiy:
>> This should prevent the destination guest from misbehaving when
>> the threads number is different in "-smp" command.
>
> Sorry, I don't understand. When migrating, surely -smp needs to be the
> same on source and destination, so how can they differ?
The idea is that "-smp" does not migrate and if we run source and
destination guests with different numbers in -smp, we end up with weird
machine because interrupt server properties (gserver?) in the device tree
are different and no reconfiguration happens (no such mechanism as I know)
the whole XICS behaves different.
The patch just prevents migration from succeeding which seems better.
--
Alexey
next prev parent reply other threads:[~2014-03-27 12:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 2:41 [Qemu-devel] [PATCH] target-ppc: Add @cpu_dt_id into migration stream Alexey Kardashevskiy
2014-03-27 12:37 ` Andreas Färber
2014-03-27 12:49 ` Alexey Kardashevskiy [this message]
2014-03-27 12:57 ` Peter Maydell
2014-03-27 13:07 ` Alexey Kardashevskiy
2014-04-08 1:26 ` Alexey Kardashevskiy
2014-04-10 12:10 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2014-04-10 14:35 ` Alexey Kardashevskiy
2014-04-10 14:41 ` Alexander Graf
2014-04-10 14:44 ` Alexey Kardashevskiy
2014-04-10 14:49 ` Peter Maydell
2014-04-10 15:11 ` Alexey Kardashevskiy
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=53341E41.7050101@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=afaerber@suse.de \
--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 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.