From: William Lee Irwin III <wli@holomorphy.com>
To: Nigel Cunningham <ncunningham@users.sourceforge.net>
Cc: Linux Memory Management <linux-mm@kvack.org>
Subject: Re: Can a page be HighMem without having the HighMem flag set?
Date: Fri, 23 Jan 2004 16:04:35 -0800 [thread overview]
Message-ID: <20040124000435.GC1016@holomorphy.com> (raw)
In-Reply-To: <1074900629.2024.44.camel@laptop-linux>
On Sat, Jan 24, 2004 at 12:30:29PM +1300, Nigel Cunningham wrote:
> <4> BIOS-e820: 0000000000000000 - 000000000009e000 (usable)
> <4> BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved)
> <4> BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
> <4> BIOS-e820: 0000000000100000 - 00000000efff6500 (usable)
> <4> BIOS-e820: 00000000efff6500 - 00000000f0000000 (ACPI data)
> <4> BIOS-e820: 00000000fffb0000 - 0000000100000000 (reserved)
> <4> BIOS-e820: 0000000100000000 - 0000000400000000 (usable)
> It's the pages efff6000- which are causing me grief. if I understand
> things correctly, page_is_ram is returning 0 for those pages, and as a
> result they get marked reserved and not HighMem by one_highpage_init.
> I suppose, then, that I need to check for and ignore pages >
> highstart_pfn where PageHighMem is not set/Reserved is set. (Either
> okay?).
If it's reserved, most/all bets are off -- only the "owner" of the thing
understands what it is. Some more formally-defined semantics for reserved
are needed, but 2.6 is unlikely to get them soon.
-- wli
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-01-24 0:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 2:26 Nigel Cunningham
2004-01-23 2:26 ` William Lee Irwin III
2004-01-23 2:46 ` Nigel Cunningham
2004-01-23 3:30 ` Nigel Cunningham
2004-01-23 23:30 ` Nigel Cunningham
2004-01-24 0:04 ` William Lee Irwin III [this message]
2004-01-24 0:20 ` Nigel Cunningham
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=20040124000435.GC1016@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-mm@kvack.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