From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
Jacob Shin <jacob.shin@amd.com>, Tom Rini <trini@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@kernel.org" <stable@kernel.org>
Subject: Re: BUG: 1bbbbe7 (x86: Exclude E820_RESERVED regions...) PANIC on boot
Date: Mon, 22 Oct 2012 14:27:38 -0700 [thread overview]
Message-ID: <5085BA4A.30800@zytor.com> (raw)
In-Reply-To: <CAE9FiQVt5LN6_wDvS2G+UULD4Ba2CF=zLhg4RULSKbfbct0NLg@mail.gmail.com>
On 10/22/2012 02:25 PM, Yinghai Lu wrote:
> On Mon, Oct 22, 2012 at 1:52 PM, H. Peter Anvin <hpa@linux.intel.com> wrote:
>> On 10/22/2012 01:50 PM, Yinghai Lu wrote:
>>> ok, let's see if we can meet this extreme corner case except user
>>> specify not page aligned "memmap="
>>
>> If it is *only* memmap= there is a very simple solution: if the memmap
>> is RAM then we round up the starting address and round down the end
>> address; if the memmap is not RAM then we round up instead...
>
> We never know that bios guys will not let bios produce crazy e820 map.
>
Yeah, well, that just *will* happen... that's a given.
We can trim those ranges, though. Who cares if we lose some RAM.
-hpa
next prev parent reply other threads:[~2012-10-22 21:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <903a3ead-98b5-4afa-88a4-3dc723895e82@blur>
[not found] ` <d556fc0f-da5d-4531-b331-6dc086461f34@blur>
2012-10-21 0:17 ` BUG: 1bbbbe7 (x86: Exclude E820_RESERVED regions...) PANIC on boot Tom Rini
2012-10-21 4:01 ` Yinghai Lu
2012-10-21 4:18 ` Jacob Shin
2012-10-21 17:51 ` Tom Rini
2012-10-21 21:06 ` Jacob Shin
2012-10-21 21:23 ` Tom Rini
2012-10-22 14:40 ` Jacob Shin
2012-10-22 18:05 ` Yinghai Lu
2012-10-22 18:38 ` Jacob Shin
2012-10-22 19:46 ` Yinghai Lu
2012-10-22 20:26 ` H. Peter Anvin
2012-10-22 20:50 ` Yinghai Lu
2012-10-22 20:52 ` H. Peter Anvin
2012-10-22 21:25 ` Yinghai Lu
2012-10-22 21:27 ` H. Peter Anvin [this message]
2012-10-22 23:35 ` Yinghai Lu
2012-10-24 16:48 ` Jacob Shin
2012-10-24 18:53 ` H. Peter Anvin
2012-10-24 19:53 ` Jacob Shin
2012-10-24 21:49 ` [tip:x86/urgent] x86, mm: Find_early_table_space based on ranges that are actually being mapped tip-bot for Jacob Shin
2012-10-25 6:42 ` Yinghai Lu
2012-10-25 7:55 ` Ingo Molnar
2012-10-25 14:33 ` Yinghai Lu
2012-10-25 22:23 ` Jacob Shin
2012-10-25 23:31 ` [tip:x86/urgent] x86, mm: Undo incorrect revert in arch/x86/mm/ init.c tip-bot for Yinghai Lu
2012-10-24 19:01 ` [tip:x86/urgent] x86, mm: Trim memory in memblock to be page aligned tip-bot for Yinghai Lu
2012-10-24 19:02 ` [tip:x86/urgent] x86, mm: Use memblock memory loop instead of e820_RAM tip-bot for Yinghai Lu
2012-10-22 21:00 ` BUG: 1bbbbe7 (x86: Exclude E820_RESERVED regions...) PANIC on boot H. Peter Anvin
2012-10-22 21:06 ` Yinghai Lu
2012-10-28 20:48 ` Tom Rini
2012-10-21 17:52 ` Tom Rini
2012-10-21 0:06 Tom Rini
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=5085BA4A.30800@zytor.com \
--to=hpa@zytor.com \
--cc=hpa@linux.intel.com \
--cc=jacob.shin@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=trini@ti.com \
--cc=yinghai@kernel.org \
/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.