From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>
Cc: akpm@osdl.org, Linux Kernel <linux-kernel@vger.kernel.org>,
suresh.b.siddha@intel.com
Subject: Re: [patch] Fix BIOS-e820 end address
Date: Fri, 14 Sep 2007 14:00:02 -0700 [thread overview]
Message-ID: <46EAF652.9060405@goop.org> (raw)
In-Reply-To: <20070908205044.GA16419@askeshav-devel.jf.intel.com>
Keshavamurthy, Anil S wrote:
> Subject: [patch] Fix BIOS-e820 end address
>
> --snip of boot message--
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 000000007fe8cc00 (usable)
> ----end snip---
>
> As you see from above the address 0000000000100000 is both
> shown as reserved and usable which is confusing.
>
I think this is consistent with many other kernel interfaces (such as
/proc/X/maps) where the end address is taken to be exclusive: [0xf0000,
0x100000).
J
next prev parent reply other threads:[~2007-09-14 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 20:50 [patch] Fix BIOS-e820 end address Keshavamurthy, Anil S
2007-09-08 7:05 ` Jan Engelhardt
2007-09-14 21:00 ` Jeremy Fitzhardinge [this message]
2007-09-14 21:31 ` Siddha, Suresh B
2007-09-14 21:31 ` Keshavamurthy, Anil S
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=46EAF652.9060405@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@intel.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