From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Oren Laadan <orenl@cs.columbia.edu>,
xemul@parallels.com, containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, hch@infradead.org,
akpm@linux-foundation.org, torvalds@linux-foundation.org,
mingo@elte.hu
Subject: Re: [PATCH 10/30] cr: core stuff
Date: Tue, 14 Apr 2009 09:39:50 -0700 [thread overview]
Message-ID: <1239727190.32604.72.camel@nimitz> (raw)
In-Reply-To: <20090414160003.GD27461@x200.localdomain>
On Tue, 2009-04-14 at 20:00 +0400, Alexey Dobriyan wrote:
> > Are you suggesting that conversion of a checkpoint image from an older
> > version to a newer version be done in the kernel ?
>
> For mainline kernel it's completely unrealistic to support all backwards
> compatibility code for previous versions. Some mythical userspace
> program will convert images.
>
> But it's completely realistic and much easier for distro kernel because
> distro kernel doesn't generally include patches with significant in-kernel
> internals changes, so they simply can support
> '2.6.26-1-amd64' => '2.6.26-2-amd64' situation.
>
> Distros can write conversion program too, but I don't expect they will.
Yeah, I'm with you on this. If distros ever start to care about c/r
*that* much, they'll start making this part of their testing process.
Personally, I think just giving a kernel version is pretty worthless
these days. People do tons of stuff to the kernel without bumping it at
all.
-- Dave
next prev parent reply other threads:[~2009-04-14 16:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 2:35 [PATCH 10/30] cr: core stuff Alexey Dobriyan
2009-04-10 9:35 ` Ingo Molnar
2009-04-10 11:43 ` Alexey Dobriyan
2009-04-10 16:19 ` Brian Haley
2009-04-13 8:10 ` Alexey Dobriyan
2009-04-13 21:47 ` Serge E. Hallyn
2009-04-14 5:52 ` Oren Laadan
2009-04-14 15:29 ` Serge E. Hallyn
2009-04-14 16:37 ` "partial" container checkpoint Dave Hansen
2009-04-14 17:30 ` Kevin Fox
2009-04-15 0:06 ` Paul Menage
2009-04-14 15:27 ` [PATCH 10/30] cr: core stuff Alexey Dobriyan
2009-04-14 15:41 ` Dave Hansen
2009-04-14 16:57 ` Alexey Dobriyan
2009-04-14 15:41 ` Serge E. Hallyn
2009-04-14 16:48 ` Dave Hansen
2009-04-14 17:00 ` Alexey Dobriyan
2009-04-14 17:04 ` Alexey Dobriyan
2009-04-14 17:23 ` checkpoint/restart: taking refcounts on kernel objects Dave Hansen
2009-05-01 12:56 ` Alexey Dobriyan
2009-04-14 17:43 ` [PATCH 10/30] cr: core stuff Oren Laadan
2009-04-14 5:22 ` Oren Laadan
2009-04-14 16:00 ` Alexey Dobriyan
2009-04-14 16:39 ` Dave Hansen [this message]
2009-04-14 17:28 ` Alexey Dobriyan
2009-04-14 18:19 ` Oren Laadan
2009-04-14 19:00 ` Alexey Dobriyan
2009-04-14 19:26 ` Oren Laadan
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=1239727190.32604.72.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=orenl@cs.columbia.edu \
--cc=torvalds@linux-foundation.org \
--cc=xemul@parallels.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox