From: Andrew Morton <akpm@osdl.org>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: mrustad@mac.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.16 hugetlbfs problem - DEBUG_PAGEALLOC
Date: Sat, 25 Mar 2006 00:15:19 -0800 [thread overview]
Message-ID: <20060325001519.45a6e150.akpm@osdl.org> (raw)
In-Reply-To: <200603250728.k2P7Sog25321@unix-os.sc.intel.com>
"Chen, Kenneth W" <kenneth.w.chen@intel.com> wrote:
>
> Andrew Morton wrote on Friday, March 24, 2006 6:54 PM
> > "Chen, Kenneth W" <kenneth.w.chen@intel.com> wrote:
> > >
> > > Mark Rustad wrote on Friday, March 24, 2006 9:52 AM
> > > > I have narrowed this down to DEBUG_PAGEALLOC. If that option is
> > > > enabled, attempts to reference areas mmap-ed from hugetlbfs files
> > > > fault forever. You can see that I had that set in the failing config
> > > > I reported below.
> > >
> > > Yeah, it turns out that the debug option is not compatible with hugetlb
> > > page support. That debug option turns off PSE. Once it is turned off in
> > > CR4, cpu will ignore pse bit in the pmd and causing infinite page-not-
> > > present fault :-(
> >
> > I wonder if any of the other architectures which implement both these
> > features might have problems too.
>
>
> Only 32-bit x86 arch implements both. We get away by not having DEBUG_PAGEALLOC
> feature on any other arch.
OK, thanks.
> ...
> I was going to verify that on my ia32 box, but apparently, turning on
> 64G highmem gives me machine reset at boot. (is it a known regression?)
Works OK here.
quad:/home/akpm> cat /proc/meminfo
MemTotal: 7251348 kB
MemFree: 7180680 kB
Buffers: 18868 kB
Cached: 20980 kB
SwapCached: 0 kB
Active: 32100 kB
Inactive: 14440 kB
HighTotal: 6422528 kB
HighFree: 6390924 kB
LowTotal: 828820 kB
LowFree: 789756 kB
SwapTotal: 4000040 kB
SwapFree: 4000040 kB
Dirty: 128 kB
Writeback: 0 kB
Mapped: 10112 kB
Slab: 11352 kB
CommitLimit: 7625712 kB
Committed_AS: 15292 kB
PageTables: 520 kB
VmallocTotal: 118776 kB
VmallocUsed: 2180 kB
VmallocChunk: 116356 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
Hugepagesize: 2048 kB
prev parent reply other threads:[~2006-03-25 8:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 22:10 2.6.16 hugetlbfs problem Mark Rustad
2006-03-22 22:13 ` David S. Miller
2006-03-22 23:32 ` Mark Rustad
2006-03-23 5:43 ` Chen, Kenneth W
2006-03-23 15:36 ` Mark Rustad
2006-03-23 19:13 ` Mark Rustad
2006-03-24 17:52 ` 2.6.16 hugetlbfs problem - DEBUG_PAGEALLOC Mark Rustad
2006-03-25 1:24 ` Chen, Kenneth W
2006-03-25 1:47 ` David S. Miller
2006-03-25 2:53 ` Andrew Morton
2006-03-25 7:29 ` Chen, Kenneth W
2006-03-25 8:15 ` Andrew Morton [this message]
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=20060325001519.45a6e150.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrustad@mac.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
Powered by JetHome