mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Nigel Cunningham <ncunningham@cyclades.com>
Cc: Andrew Morton <akpm@osdl.org>,
	mjg59@scrf.ucam.org, hare@suse.de,
	"Barry K. Nathan" <barryn@pobox.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: swsusp: allow resume from initramfs
Date: Fri, 4 Mar 2005 23:07:09 +0100	[thread overview]
Message-ID: <20050304220709.GE2385@elf.ucw.cz> (raw)
In-Reply-To: <1109973035.3772.291.camel@desktop.cunningham.myip.net.au>

Hi!

> > > You guys are reinventing the wheel a lot at the moment and I'm in the
> > > middle of doing it for x86_64 lowlevel code :> Can we see if we can work
> > > a little more closely - perhaps we can get some shared code going that
> > > will allow us to handle these issues without stepping on each others'
> > > feet? In particular, shared code for
> > > 
> > > - initramfs and initrd support
> > 
> > Its actually done, and it was few strategically placed lines of code
> > (like 20 lines). I do not think it can be meaningfully shared.
> 
> Mmm. But if we're both putting hooks in the same places...

There are very little hooks... But we may want to make sure we have
same userland interface. swsusp uses "echo 3:5 > /sys/power/resume" to
trigger resume from device major 3 minor 5.

> > > - lowlevel suspend & resume
> > 
> > This makes very good sense to share. We have i386, x86-64 and ppc
> > versions. They simply walk list of pbe's; that should be simple enough
> > to be usable for suspend2, too....
> 
> The CPU save and restore, yes. But I use a different format for
> recording the image metadata (I use bitmaps to record the locations of
> pages). Perhaps I should hasten to mention the bitmaps are discontiguous
> - single pages connected by a kmalloc'd list. The copyback itself will
> need to stay distinct.

Hmm, bitmaps? Okay, then low-level code needs to stay separate. (And
thats bad, I wanted that one to be shared most).
								Pavel

-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

  reply	other threads:[~2005-03-05  0:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 10:16 Pavel Machek
2005-03-04 11:04 ` Andrew Morton
2005-03-04 11:15   ` Pavel Machek
2005-03-04 17:17   ` Stefan Seyfried
2005-03-04 17:50   ` Barry K. Nathan
2005-03-04 21:22     ` Nigel Cunningham
2005-03-04 21:43       ` Pavel Machek
2005-03-04 21:50         ` Nigel Cunningham
2005-03-04 22:07           ` Pavel Machek [this message]
2005-03-04 22:31             ` Nigel Cunningham
2005-03-04 22:55               ` Pavel Machek
2005-03-05  1:07                 ` Nigel Cunningham
2005-03-05 21:58                   ` swsusp memory freeing [was Re: swsusp: allow resume from initramfs] Pavel Machek
2005-03-06 22:28   ` swsusp: allow resume from initramfs Andreas Jellinghaus
2005-03-06 22:27 ` Andreas Jellinghaus
2005-03-07 11:40   ` Pavel Machek
     [not found] <fa.e8vvlml.hjolb5@ifi.uio.no>
     [not found] ` <fa.h2h05q4.mmkqpm@ifi.uio.no>
2005-03-04 13:36   ` Bodo Eggert

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=20050304220709.GE2385@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=akpm@osdl.org \
    --cc=barryn@pobox.com \
    --cc=hare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@scrf.ucam.org \
    --cc=ncunningham@cyclades.com \
    /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

all inboxes | Powered by JetHome®