All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Alexander Graf <agraf@suse.de>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Jens Freimann <jfrei@linux.vnet.ibm.com>,
	"Jason J. Herne" <jjherne@linux.vnet.ibm.com>,
	Boris Fiuczynski <fiuczy@linux.vnet.ibm.com>,
	Cornelia Huck <cornelia.huck@de.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] s390x/migration: Introduce 2.4 machine
Date: Wed, 01 Jul 2015 11:56:34 +0200	[thread overview]
Message-ID: <87egks19rh.fsf@neno.neno> (raw)
In-Reply-To: <1435742217-62246-1-git-send-email-borntraeger@de.ibm.com> (Christian Borntraeger's message of "Wed, 1 Jul 2015 11:16:57 +0200")

Christian Borntraeger <borntraeger@de.ibm.com> wrote:

First of all

Reviewed-by: Juan Quintela <quintela@redhat.com>

For the patch.

But one said that, I don't agree with the commint text.


> The section footer changes commit f68945d42bab ("Add a protective
> section footer") and commit 37fb569c0198 ("Disable section footers
> on older machine types") broke migration for any non-versioned
> machines.

If broke migration for 2.4 -> 2.3 for machines that don't care about
compatibility.  If they care, they are versioned O:-)  Right now ppc &
x86.  I guess that s390 and arm will follow in due curse.

> While one can argue that section footer should be enabled
> explicitely for new versions instead of disabled for old ones,
> this pinpoints to a problem of s390-ccw-machines: it needs to
> be versioned to be compatible with future changes in common
> code data structures such as section footers.

It is done explicitely the other way around.  New way is the default
way.  If we did it in a special way in the past, we add a switch.  If at
some point we remove the old machine type for any reason, we don't have
to change anything on $latest.

Basically the idea here is that (until now) only x86 cared about
backwards compatibility, so when a migration changed happened because it
was good for any reason, normal devices do changes, and then x86 try to
fix the pieces after the fact.  That is going to continue, just that now
more architectures care, and then we should detect this kind of problems
much earlier.

> Let's introduce a version scheme for s390-ccw-virtio machines.
> We will use the old s390-ccw-virtio name as alias to the latest
> version as all existing libvirt XML for the ccw type were expanded
> by libvirt to that name.
>
> The only downside of this patch is, that the old alias s390-ccw
> will no longer be available as machines can have only one alias,
> but it should not really matter.

Should we change to a list?

Later, Juan.

  reply	other threads:[~2015-07-01  9:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01  9:16 [Qemu-devel] [PATCH 1/1] s390x/migration: Introduce 2.4 machine Christian Borntraeger
2015-07-01  9:56 ` Juan Quintela [this message]
2015-07-01 10:20   ` Christian Borntraeger
2015-07-01 11:10     ` Juan Quintela
2015-07-01 12:33 ` Cornelia Huck

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=87egks19rh.fsf@neno.neno \
    --to=quintela@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=dgilbert@redhat.com \
    --cc=fiuczy@linux.vnet.ibm.com \
    --cc=jfrei@linux.vnet.ibm.com \
    --cc=jjherne@linux.vnet.ibm.com \
    --cc=qemu-devel@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.