From: Ralf Baechle <ralf@linux-mips.org>
To: Wu Zhangjin <wuzhangjin@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-mips@linux-mips.org,
Sergei Shtylyov <sshtylyov@ru.mvista.com>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH -v1] MIPS: fix pfn_valid() for FLATMEM
Date: Wed, 14 Oct 2009 00:04:17 +0200 [thread overview]
Message-ID: <20091013220417.GA32099@linux-mips.org> (raw)
In-Reply-To: <1255104130.3658.122.camel@falcon>
On Sat, Oct 10, 2009 at 12:02:10AM +0800, Wu Zhangjin wrote:
> The above patch can not fix the problem when enabled FLATMEM in
> linux-2.6.32-rc3, the real problem should be that we need register the
> "pci memory space" as nosave pages, and also, the above "reserved"(not
> memory) pages should be registered as nosave pages. but the simpler
> solution should be the pfn_valid() I sent out in this E-mail thread, we
> just need to check whether they are "valid", if they are "System
> RAM"(BOOT_MEM_RAM or BOOT_MEM_ROM_DATA), they should be valid.
>
> and what's more? should be register "pci memory space" as nosave pages
> for all architecture?
No. You only see this problem because your PCI memory space is between
the lowest and the highest memory address. Other systems don't have this
issue because they either use the discontig or sparse memory models.
Btw, for systems that actually have memory in the 90000000-bfffffff range
and are running a 64-bit kernel with 4k ages the flatmem memory model
will waste 28MB of RAM; with 16k pages it's still 7MB.
Time to say gooebye to flatmem?
Ralf
next prev parent reply other threads:[~2009-10-13 22:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 11:32 [PATCH -v1] MIPS: fix pfn_valid() for FLATMEM Wu Zhangjin
2009-10-08 20:21 ` Rafael J. Wysocki
2009-10-08 20:44 ` Ralf Baechle
2009-10-09 2:08 ` Wu Zhangjin
2009-10-09 16:02 ` Wu Zhangjin
2009-10-13 22:04 ` Ralf Baechle [this message]
2009-10-14 1:06 ` Wu Zhangjin
-- strict thread matches above, loose matches on Subject: below --
2009-10-09 16:15 Wu Zhangjin
2009-10-09 16:20 ` Wu Zhangjin
2009-10-10 14:38 ` Wu Zhangjin
2009-10-10 19:19 ` Wu Zhangjin
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=20091013220417.GA32099@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=sshtylyov@ru.mvista.com \
--cc=wuzhangjin@gmail.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;
as well as URLs for NNTP newsgroup(s).