[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <51277F77.2090908@redhat.com>
Date: Fri, 22 Feb 2013 15:23:51 +0100
From: Denys Vlasenko <dvlasenk@...hat.com>
To: u3557@...lix.com.au
CC: Amnon Shiloh <u3557@...o.sublimeip.com>,
Steven Rostedt <rostedt@...dmis.org>,
Oleg Nesterov <oleg@...hat.com>,
Pedro Alves <palves@...hat.com>,
Jan Kratochvil <jan.kratochvil@...hat.com>,
Cyrill Gorcunov <gorcunov@...nvz.org>,
Pavel Emelyanov <xemul@...allels.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
linux-kernel@...r.kernel.org
Subject: Re: prctl(PR_SET_MM)
On 02/19/2013 07:25 AM, Amnon Shiloh wrote:
> Steven Rostedt wrote:
>
>> If only you, or a few people are using it (ie. distros don't see a
>> need), then it will be up to you to make the changes.
>
> I believe that this functionality is of a general nature and is needed
> by many, not only by myself and by the CRIU group, but by all user-level
> software packages, past present and future, that provide some form or
> another of reconstructing a Linux process.
That's what "RESTORE" part of CONFIG_CHECKPOINT_RESTORE refers to:
the ability to restore (reconstruct) a process.
If you want to be able to restore a process, you need RESTORE
feature. It's that simple.
Why do you want yet another config option for it?
What's the problem if you simply enable CONFIG_CHECKPOINT_RESTORE?
The only problem I can imagine is "CONFIG_CHECKPOINT_RESTORE
enables too many things I don't need".
Frankly, I find it not very likely, unless you are planning
on working on resource-constrained machines (like mobile phone).
--
vda
--
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