From: Pavel Machek <pavel@suse.cz>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: William Lee Irwin III <wli@holomorphy.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] swsuspend and CONFIG_DISCONTIGMEM=y
Date: Fri, 15 Nov 2002 19:12:47 +0100 [thread overview]
Message-ID: <20021115181247.GB8763@elf.ucw.cz> (raw)
In-Reply-To: <1037366172.877.30.camel@zion>
Hi!
> > > > The following dropped hunk from Pavel should repair it:
> > >
> > > [cc: list trimmed to spare the uninterested]
> > >
> > > Hmm, there are some oddities here in count_and_copy_data_pages(). It
> > > looks like the CONFIG_HIGHMEM panic() is there because copy_page() is
> > > done without kmapping, and the CONFIG_DISCONTIGMEM panic() is there
> > > because the pgdat list etc. are not walked according to VM
> > > conventions.
> >
> > How much memory is needed for HIGHMEM to be neccessary? Is it 1GB? If
> > so, I can well imagine 1GB laptop....
>
> Depends on the arch & other matters. 768Mb on PPC at least, and
> it starting to be common within laptops as well.
I just hope we'll never ever see 64GB i386 laptop...
... We'll probably have to write simpler equivalent of kmap_atomic for
use in suspend_asm.S. It is not really *so* deep magic.
> > This certainly does not work. We'd need to do some deep magic in
> > suspend_asm.S to copy pages back. [Well, deep magic... Same
> > kmap_atomic.] But suspend_asm.S has to guarantee not touching any
> > memory so the change is not quite trivial.
>
> At worst, that could be an arch provided routine. On most PPC32's
> I can then just disable data translation on the MMU and access
> all pages without kmap'ing them. But that's not terribly portable
> and each arch would need different kind of hacking.
It is arch-specific already. What's worse, resume has to be written in
assembly, so you can't simply write kmap_atomic() there. See
arch/i386/kernel/suspend_asm.S.
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
next prev parent reply other threads:[~2002-11-15 18:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 8:10 Arnaldo Carvalho de Melo
2002-11-15 8:49 ` William Lee Irwin III
2002-11-15 9:48 ` William Lee Irwin III
2002-11-15 12:02 ` Pavel Machek
2002-11-15 12:09 ` William Lee Irwin III
2002-11-15 18:09 ` Pavel Machek
2002-11-15 18:33 ` William Lee Irwin III
2002-11-15 13:16 ` Benjamin Herrenschmidt
2002-11-15 18:12 ` Pavel Machek [this message]
2002-11-15 18:56 ` William Lee Irwin III
2002-11-16 2:41 ` Alan Cox
2002-11-16 3:06 ` William Lee Irwin III
2002-11-16 17:35 ` Oliver Xymoron
2002-11-15 11:54 ` Pavel Machek
2002-11-15 11:57 ` Arnaldo Carvalho de Melo
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=20021115181247.GB8763@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
/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
all inboxes | Powered by JetHome®