From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Pavel Machek <pavel@ucw.cz>
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 19:21:19 +1100 [thread overview]
Message-ID: <1074846066.789.3.camel@gaston> (raw)
In-Reply-To: <20040123075451.GB211@elf.ucw.cz>
> Now, I'm apparently rewriting swapper_pg_dir with itself (same
> data). That's not too clean, but CPUs do not notice it...
Well... ok, you _hope_ it's same data :) I suppose with same kernel,
same text and same amount of RAM, you indeed have the same data, though
this is a bit hairy.
For PPC, I have to go to a different way though. I'll probably end up
allocating a small hash table for G5 like CPUs on resume outside of
the space that gets overwriten, though that is definitely a bit nasty,
since the minimum size of a hash table is 256K, so I'll need that
contiguous at least...
For now, I'm just disabling the data translation on the MMU and
assume the BAT is covering me for resume, but that's a bit hairy
too and definitely slow on some CPUs
Ben.
next prev parent reply other threads:[~2004-01-23 8:21 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 [this message]
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=1074846066.789.3.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.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