linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier.adi@gmail.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Pavel Machek <pavel@ucw.cz>,
	Nigel Cunningham <ncunningham@crca.org.au>,
	Hugh Dickins <hugh.dickins@tiscali.co.uk>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: swsusp on nommu, was 'Re: No more bits in vm_area_struct's vm_flags.'
Date: Wed, 30 Sep 2009 12:06:58 -0400	[thread overview]
Message-ID: <8bd0f97a0909300906k283e3fd2q80705dbf78588cac@mail.gmail.com> (raw)
In-Reply-To: <20090930130815.GA4134@cmpxchg.org>

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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2009-09-30 15:53 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4AB9A0D6.1090004@crca.org.au>
2009-09-23 20:23 ` No more bits in vm_area_struct's vm_flags Hugh Dickins
2009-09-25  8:30   ` Nigel Cunningham
2009-09-25 11:36     ` Hugh Dickins
2009-09-25 11:47       ` Nigel Cunningham
2009-09-30 12:02     ` Pavel Machek
2009-09-30 13:08       ` swsusp on nommu, was 'Re: No more bits in vm_area_struct's vm_flags.' Johannes Weiner
2009-09-30 16:06         ` Mike Frysinger [this message]
2009-09-24  1:05 ` No more bits in vm_area_struct's vm_flags KAMEZAWA Hiroyuki
2009-09-25  8:34   ` Nigel Cunningham
2009-09-25  8:40     ` KAMEZAWA Hiroyuki
2009-09-25  8:48       ` Nigel Cunningham
2009-09-25 21:09         ` Joerg Roedel
2009-09-28  2:45       ` Nigel Cunningham
2009-09-28  3:04         ` KAMEZAWA Hiroyuki
2009-09-28  3:36           ` Wu Fengguang
2009-09-28  3:57             ` KAMEZAWA Hiroyuki
2009-09-28  4:37               ` Nigel Cunningham
2009-09-28  4:51                 ` Wu Fengguang
2009-09-28  4:53                 ` KAMEZAWA Hiroyuki
2009-09-28  5:22                   ` Nigel Cunningham
2009-09-28  5:32                     ` KAMEZAWA Hiroyuki
2009-09-28 21:21                 ` Hugh Dickins
2009-09-28 21:33                   ` Nigel Cunningham
2009-09-28 15:38               ` Hugh Dickins
2009-09-28 16:14                 ` KAMEZAWA Hiroyuki
2009-09-28 21:00                   ` Hugh Dickins
2009-09-28 21:22                     ` Nigel Cunningham
2009-09-29  1:57                     ` KAMEZAWA Hiroyuki
2009-09-29 14:22                       ` Christoph Lameter
2009-10-01 10:54                         ` Hugh Dickins
2009-10-01 13:47                           ` Christoph Lameter
2009-10-01 11:38                       ` Hugh Dickins
2009-10-02  0:42                         ` KAMEZAWA Hiroyuki
2009-10-02  1:37                           ` KAMEZAWA Hiroyuki
2009-10-02  2:39                             ` KAMEZAWA Hiroyuki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8bd0f97a0909300906k283e3fd2q80705dbf78588cac@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=hugh.dickins@tiscali.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ncunningham@crca.org.au \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).