All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
	"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	"Alexander Graf" <agraf@suse.de>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] target-ppc: Add @cpu_dt_id into migration stream
Date: Fri, 11 Apr 2014 01:11:37 +1000	[thread overview]
Message-ID: <5346B4A9.7040601@ozlabs.ru> (raw)
In-Reply-To: <CAFEAcA_p9PF=n8DBW1pV=EENBb-dVsRmmP=_bhRGnZajDZ9Apw@mail.gmail.com>

On 04/11/2014 12:49 AM, Peter Maydell wrote:
> On 10 April 2014 15:35, Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
>> Then what is the purpose of many, many VMSTATE_.*_EQUAL?
> 
> Often it's backwards compatibility with a previous vmstate
> or save/load function set which incorrectly sent data it didn't
> need to.
> 
>> And I do not want to send configuration by the proposed patch, I want to
>> make sure that the new guest is able to continue. Why exactly is this bad?
> 
> It's not bad, but as several people have now pointed out to you,
> you're trying to fix a tiny tiny corner of the real, larger
> problem, in a way which isn't going to generalise to actually
> fixing the larger problem. So if we took your change then
> (a) we still wouldn't be able to support detection of migration
> between two systems with mismatched configuration, so it doesn't
> really achieve anything
> (b) if we ever did manage to fix that we'd have to remove your
> change (because that bit of config checking would now be handled
> via whatever generic mechanism we implemented), except we probably
> couldn't remove it since that would break migration version
> compatibility, so we'd end up with a wart we have to carry
> around forever

Ok, understood. Thanks.


ps. yeah, I do not often see the bigger picture, I know :(
-- 
Alexey

      reply	other threads:[~2014-04-10 15:11 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
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 [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=5346B4A9.7040601@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=peter.maydell@linaro.org \
    --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.