public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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:54:51 +0100	[thread overview]
Message-ID: <20040123075451.GB211@elf.ucw.cz> (raw)
In-Reply-To: <1074843781.878.1.camel@gaston>

Hi!

> > 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.
> 
> Just enlighten me please: How do these 4Mb page tables work ? The pgdir
> entries contain special bits ? Then you at least must make sure the

The pgdir contains special bits, and there are no other levels of page
tables.

Now, I'm apparently rewriting swapper_pg_dir with itself (same
data). That's not too clean, but CPUs do not notice it...

> 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.
								Pavel
-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

  reply	other threads:[~2004-01-23  7:55 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 [this message]
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=20040123075451.GB211@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox