public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@karaya.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Adam Feuer <adamf@pobox.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Swsusp mailing list <swsusp@lister.fornax.hu>,
	ACPI mailing list <acpi@phobos.fachschaften.tu-muenchen.de>,
	kernel list <linux-kernel@vger.kernel.org>,
	Gabor Kuti <seasons@falcon.sch.bme.hu>
Subject: Re: [swsusp] Re: swsusp for 2.4.14
Date: Wed, 21 Nov 2001 13:53:13 -0500	[thread overview]
Message-ID: <200111211853.NAA03050@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Wed, 21 Nov 2001 16:46:20 +0100." <20011121164620.D31379@atrey.karlin.mff.cuni.cz>

pavel@suse.cz said:
> Yep, I'd like to see it. [The way uml is setup with one uml kernel
> running in *many* real processes, saving/restoring cpu state is not
> going to be easy.]

It won't be horrible.  You have to recreate all the processes (and getting
their address spaces mapped correctly should be easy) and get them all
ptraced by the tracing thread.  UML processes which are CLONE_VM are also
CLONE_VM on the host, so that will take a little bit of care.

Devices will need to be reopened as well.

				Jeff


  reply	other threads:[~2001-11-21 17:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-20 23:18 swsusp for 2.4.14 Pavel Machek
2001-11-21  0:50 ` H. Peter Anvin
2001-11-21  1:24 ` Alan Cox
2001-11-21  2:07   ` [swsusp] " Adam Feuer
2001-11-21  4:12     ` Jeff Dike
2001-11-21  2:47       ` undocumented, ungoogleable /proc/net/nicinfo interface Blue Lang
2001-11-21 15:46     ` [swsusp] Re: swsusp for 2.4.14 Pavel Machek
2001-11-21 18:53       ` Jeff Dike [this message]
2001-11-23 13:46         ` Pavel Machek
2001-11-25  0:50           ` Jeff Dike
2001-11-21 15:45   ` Pavel Machek

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=200111211853.NAA03050@ccure.karaya.com \
    --to=jdike@karaya.com \
    --cc=adamf@pobox.com \
    --cc=pavel@suse.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