From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758487Ab3BTIkE (ORCPT ); Wed, 20 Feb 2013 03:40:04 -0500 Received: from mail-lb0-f174.google.com ([209.85.217.174]:62384 "EHLO mail-lb0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756340Ab3BTIkC (ORCPT ); Wed, 20 Feb 2013 03:40:02 -0500 Date: Wed, 20 Feb 2013 12:39:58 +0400 From: Cyrill Gorcunov To: Amnon Shiloh Cc: Steven Rostedt , u3557@dialix.com.au, Oleg Nesterov , Pedro Alves , Denys Vlasenko , Jan Kratochvil , Pavel Emelyanov , Frederic Weisbecker , Ingo Molnar , Peter Zijlstra , linux-kernel@vger.kernel.org Subject: Re: prctl(PR_SET_MM) Message-ID: <20130220083958.GS20312@moon> References: <1361216963.23152.168.camel@gandalf.local.home> <20130219062531.4F317592076@miso.sublimeip.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130219062531.4F317592076@miso.sublimeip.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 19, 2013 at 05:25:31PM +1100, Amnon Shiloh wrote: > > To reconstruct Linux process(es), one must be able to restore all their > memory contents, states and registers to their original and consistent > values. I personally don't mind if this come become y by default, because it will work for us. Still I guess if you need to reconstruct Linux process(es) plain prctl extension is not enough, you still need a functionality which is enclosed in config-checkpoint-restore (say /proc/pid/map_files, kcmp), no?