From: Pavel Machek <pavel@ucw.cz>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Nigel Cunningham <ncunningham@users.sourceforge.net>,
Patrick Mochel <mochel@osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: swsusp vs pgdir
Date: Fri, 23 Jan 2004 08:34:26 +0100 [thread overview]
Message-ID: <20040123073426.GA211@elf.ucw.cz> (raw)
In-Reply-To: <1074833921.975.197.camel@gaston>
Hi!
> I've been bored enough today to hack on getting the current
> pmdisk/swsusp up on ppc. The required arch code should be almost
> identical.
>
> However, when looking at it, I didn't fully understand how you
> actually ensure your page mappings aren't beeing blown away
> behind your back during the copy operation on resume, but since
> my knowledge of x86 is almost inexistant, I didn't decipher this
> from the source code. Could you explain a bit ?
>
> The thing is that you seem to point to the swapper pgdir during
> the copy, that is the kernel page tables, but those are beeing
> wiped out during the copy potentially, no ?
We test that CPU has PSE feature. That means kernel is mapped using
4MB page tables, and I do not have to care about page tables at
all.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-01-23 7:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 4:58 swsusp vs pgdir Benjamin Herrenschmidt
2004-01-23 7:34 ` Pavel Machek [this message]
2004-01-23 7:43 ` Benjamin Herrenschmidt
2004-01-23 7:54 ` Pavel Machek
2004-01-23 8:21 ` Benjamin Herrenschmidt
2004-01-23 16:03 ` Patrick Mochel
2004-01-23 16:10 ` Benjamin Herrenschmidt
2004-01-23 16:45 ` Patrick Mochel
2004-01-23 16:53 ` Pavel Machek
2004-01-23 17:04 ` Pavel Machek
2004-01-24 1:03 ` Benjamin Herrenschmidt
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=20040123073426.GA211@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=ncunningham@users.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.