mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Chris Lalancette <chris.lalancette@gd-ais.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory image save/restore
Date: Thu, 15 Apr 2004 16:02:25 +0200	[thread overview]
Message-ID: <20040415140225.GN468@openzaurus.ucw.cz> (raw)
In-Reply-To: <407C18D0.9010302@gd-ais.com>

Hi!

>    I have been trying to implement some sort of save/restore kernel 
> memory image for the linux kernel (x86 only right now), without much 
> success.  Let me explain the situation:
> 
> I have a hardware device that I can generate interrupts with.  I also 
> have a machine with 512M of memory, and I am passing the kernel the 
> command line mem=256M.  My idea is to generate an interrupt with the 
> hardware device, and then inside of the interrupt handler make a copy 
> of the entire contents of RAM into the unused upper 256M of memory; 
> later on, with another interrupt, I would like to restore that 
> previously saved memory image.  This way we can go "back in time", 
> similar to what software suspend is doing, but without as many 
> constraints (i.e. we have a hardware interrupt to work with, we 
> reserved the same amount of physical memory to use, etc.).  Before I 
> went much further, I figured I would ask if anyone on the list has 
> tried this, and if there are any reasons why this is not possible.

As swsusp shows, it definitely is possible...

...if you can live with system unresponsive for few seconds while it
does snapshotting.

Creating "bastardized swsusp" would actually be good way to start.
-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         


      parent reply	other threads:[~2004-04-15 20:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13 16:44 Chris Lalancette
2004-04-13 17:03 ` Paulo Marques
2004-04-13 18:22   ` Chris Lalancette
2004-04-13 19:23     ` Paulo Marques
2004-04-13 19:48     ` Adam Kropelin
2004-04-15 14:11       ` Pavel Machek
2004-04-15 14:02 ` Pavel Machek [this message]

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=20040415140225.GN468@openzaurus.ucw.cz \
    --to=pavel@suse.cz \
    --cc=chris.lalancette@gd-ais.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®