[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8bd0f97a0909300906k283e3fd2q80705dbf78588cac@mail.gmail.com>
Date: Wed, 30 Sep 2009 12:06:58 -0400
From: Mike Frysinger <vapier.adi@...il.com>
To: Johannes Weiner <hannes@...xchg.org>
Cc: Pavel Machek <pavel@....cz>,
Nigel Cunningham <ncunningham@...a.org.au>,
Hugh Dickins <hugh.dickins@...cali.co.uk>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: swsusp on nommu, was 'Re: No more bits in vm_area_struct's
vm_flags.'
On Wed, Sep 30, 2009 at 09:08, Johannes Weiner wrote:
> On Wed, Sep 30, 2009 at 02:02:03PM +0200, Pavel Machek wrote:
>> > > Does TuxOnIce rely on CONFIG_MMU? If so, then the TuxOnIce patch
>> > > could presumably reuse VM_MAPPED_COPY for now - but don't be
>> > > surprised if that's one we clean away later on.
>> >
>> > Hmm. I'm not sure. The requirements are the same as for swsusp and
>> > uswsusp. Is there some tool to graph config dependencies?
>>
>> I don't think swsusp was ported on any -nommu architecture, so config
>> dependency on MMU should be ok. OTOH such port should be doable...
>
> I am sitting on some dusty patches to split swapfile handling from
> actual paging and implement swsusp on blackfin. They are incomplete
> and I only occasionally find the time to continue working on them. If
> somebody is interested or also working on it, please let me know.
suspend to ram works on Blackfin systems w/out a problem, and i cant
think of a reason off the top of my head as to why saving/restoring
the image to disk couldnt work w/out a mmu ...
last time we looked, we found it too coupled to mmu code and we didnt
have a lot of pressure to get it done, so we moved on to other things.
-mike
--
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