From: Rusty Russell <rusty@rustcorp.com.au>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Make e820_remove_range to handle all covered case
Date: Thu, 1 Apr 2010 09:46:47 +1030 [thread overview]
Message-ID: <201004010946.47934.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4BB18E55.6090903@kernel.org>
On Tue, 30 Mar 2010 04:08:29 pm Yinghai Lu wrote:
>
> Rusty found on lguest with trim_bios_range, max_pfn is not right anymore, and
> looks e820_remove_range does not work right.
>
> [ 0.000000] BIOS-provided physical RAM map:
> [ 0.000000] LGUEST: 0000000000000000 - 0000000004000000 (usable)
> [ 0.000000] Notice: NX (Execute Disable) protection missing in CPU or disabled in BIOS!
> [ 0.000000] DMI not present or invalid.
> [ 0.000000] last_pfn = 0x3fa0 max_arch_pfn = 0x100000
> [ 0.000000] init_memory_mapping: 0000000000000000-0000000003fa0000
>
> root cause is: the e820_remove_range doesn't handle that all cover case.
> e820_remove_range(BIOS_START, BIOS_END - BIOS_start, ,,)
> get miss one left range.
>
> Make that is corresponding to e820_update_range() to handle that case too.
Tested-by: Rusty Russell <rusty@rustcorp.com.au>
Please put in -urgent...
Thanks,
Rusty.
next prev parent reply other threads:[~2010-03-31 23:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 2:08 [PATCH RFC] e820_remove_range fail? Rusty Russell
2010-03-30 4:15 ` Yinghai Lu
2010-03-30 5:38 ` [PATCH] x86: Make e820_remove_range to handle all covered case Yinghai Lu
2010-03-31 23:16 ` Rusty Russell [this message]
2010-04-01 1:00 ` [tip:x86/urgent] " tip-bot for Yinghai Lu
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=201004010946.47934.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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.