From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Patrick Mochel <mochel@digitalimplant.org>
Cc: Pavel Machek <pavel@ucw.cz>,
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: Sat, 24 Jan 2004 03:10:20 +1100 [thread overview]
Message-ID: <1074874219.835.32.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.50.0401230759180.11276-100000@monsoon.he.net>
On Sat, 2004-01-24 at 03:03, Patrick Mochel wrote:
> > > swapper_pgdir is left intact. This is the case ? (I also suppose you
> > > mean the entire linear mapping, not just the kernel, is mapped with
> > > 4M pages)
> >
> > Yes.
>
> Not necessarily. Just kernel text and data. I don't have the code in front
> of me ATM, but there are simple checks you can do to determine the
> type/size of page.
>
> We don't have to care about userspace, though, once all processes are
> frozen, so we don't have to deal with the 4k pages.
>
> And the thing is, the only reason we require PSE and 4 MB pages is because
> it provides a 2-level page table instead of a 3-level, which by
> definition is easier to manage. :)
Wait... wait... If the whole linear mapping isn't mapped by this flat
pgdir, then we have a problem, since the MMU will have to go down the
kernel pagetables to actually access the pages data when copying them
around... but at this point, we are overriding the boot kernel page
tables with the loader ones, so ...
Ben.
next prev parent reply other threads:[~2004-01-23 16:10 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
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 [this message]
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=1074874219.835.32.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=mochel@osdl.org \
--cc=ncunningham@users.sourceforge.net \
--cc=pavel@ucw.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