From: Pavel Machek <pavel@ucw.cz>
To: Nicolas Troncoso Carrere <ntroncos@alumnos.inf.utfsm.cl>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>
Subject: Re: swsusp and PSE
Date: Thu, 1 Jun 2006 16:24:18 +0200 [thread overview]
Message-ID: <20060601142418.GA24962@elf.ucw.cz> (raw)
In-Reply-To: <200606011017.22729.ntroncos@alumnos.inf.utfsm.cl>
On Čt 01-06-06 10:17:22, Nicolas Troncoso Carrere wrote:
> Hi,
> I was trying out swsusp, but up bumped up with the issue that it needs PSE.
> I've been reading the source, but havent been able to get a grasp on why does
> it need PSE.
> Could you enlighten me?
W/o PSE, we are using pagetables during data copy, and we may
overwrite pagetable that is still used.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
_______________________________________________
linux-pm mailing list
linux-pm@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/linux-pm
next prev parent reply other threads:[~2006-06-01 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 14:17 swsusp and PSE Nicolas Troncoso Carrere
2006-06-01 14:24 ` Pavel Machek [this message]
2006-06-05 1:47 ` Shaohua Li
2006-06-05 9:39 ` 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=20060601142418.GA24962@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-pm@lists.osdl.org \
--cc=ntroncos@alumnos.inf.utfsm.cl \
/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