[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m14p6xy27s.fsf@frodo.ebiederm.org>
Date: Thu, 10 Jul 2008 12:21:43 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Dave Hansen <dave@...ux.vnet.ibm.com>
Cc: "Serge E. Hallyn" <serue@...ibm.com>,
Oren Laadan <orenl@...columbia.edu>,
Kirill Korotaev <dev@...allels.com>,
containers@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org, Nadia.Derbey@...l.net,
Andrew Morton <akpm@...ux-foundation.org>,
nick@...k-andrew.net, Alexey Dobriyan <adobriyan@...il.com>
Subject: Re: Checkpoint/restart (was Re: [PATCH 0/4] - v2 - Object creation with a specified id)
Dave Hansen <dave@...ux.vnet.ibm.com> writes:
> On Thu, 2008-07-10 at 11:55 -0700, Eric W. Biederman wrote:
>>
>> > If we do checkpoint-as-a-coredump, then we need userspace to coordinate
>> > a kernel-generated coredump with a user-generated (?) swapfile snapshot.
>> > But I guess we figure that out later.
>>
>> Well it is a matter of which VMAs you dump. For things that are file backed
>> you need to dump them.
For things that are file backed you DO NOT need to dump them. (sorry typo).
> Are we talking about the VMA itself, or the memory backing the VMA?
The memory backing the VMA. We need to store the page protections
that the memory was mapped with as well now that you point it out. A
VMA is not user space visible, which is why we can arbitrarily split
and merge VMAs.
Eric
--
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