[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7d08b87d1003281555h1eb255f8ic3bcdec08008d5b2@mail.gmail.com>
Date: Mon, 29 Mar 2010 00:55:11 +0200
From: Christoffer Dall <christofferdall@...istofferdall.dk>
To: Paul Mundt <lethal@...ux-sh.org>
Cc: Jamie Lokier <jamie@...reable.org>,
Russell King - ARM Linux <linux@....linux.org.uk>,
containers <containers@...ts.linux-foundation.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [C/R ARM][PATCH 3/3] c/r: ARM implementation of
checkpoint/restart
On Fri, Mar 26, 2010 at 5:02 AM, Paul Mundt <lethal@...ux-sh.org> wrote:
> On Fri, Mar 26, 2010 at 02:47:59AM +0000, Jamie Lokier wrote:
>>
>> It's possible in principle to run many non-MMU binaries on MMU
>> kernels, but I've never heard of anyone doing it.
>>
> FDPIC supports running the same binaries with or without MMU depending on
> your ABI, it's not really that uncommon, even if it's mostly just used
> for prototyping.
>
I would imagine that the chance that a restart will fail anyway when
restoring an MMU process on a non-MMU kernel. However, as you suggest,
the other way around should be possible. Thanks for clearing that up.
Specifically, do you know the meaning of the end_brk field on the
mm_context_t struct and if I need to checkpoint it on restart for
non-MMU systems (and potentially do something more clever during
restart on an MMU kernel?)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists