From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Linux Memory Management <linux-mm@kvack.org>
Subject: Re: Can a page be HighMem without having the HighMem flag set?
Date: Sat, 24 Jan 2004 12:30:29 +1300 [thread overview]
Message-ID: <1074900629.2024.44.camel@laptop-linux> (raw)
In-Reply-To: <1074828647.12774.212.camel@laptop-linux>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
Hi all.
At boot I get:
<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?).
Regards,
Nigel
--
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-23 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 2:26 Can a page be HighMem without having the HighMem flag set? 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 [this message]
2004-01-24 0:04 ` William Lee Irwin III
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=1074900629.2024.44.camel@laptop-linux \
--to=ncunningham@users.sourceforge.net \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.