From: Wu Fengguang <fengguang.wu@intel.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
"Zheng, Shaohui" <shaohui.zheng@intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"y-goto@jp.fujitsu.com" <y-goto@jp.fujitsu.com>,
Dave Hansen <haveblue@us.ibm.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH - resend] Memory-Hotplug: Fix the bug on interface /dev/mem for 64-bit kernel(v1)
Date: Wed, 13 Jan 2010 10:29:48 +0800 [thread overview]
Message-ID: <20100113022948.GD10184@localhost> (raw)
In-Reply-To: <86802c441001121501v57b61815lc4b4c6d86dc5818d@mail.gmail.com>
On Wed, Jan 13, 2010 at 07:01:47AM +0800, Yinghai Lu wrote:
> On Tue, Jan 12, 2010 at 5:35 AM, Wu Fengguang <fengguang.wu@intel.com> wrote:
> > On Tue, Jan 12, 2010 at 10:39:03AM +0800, KAMEZAWA Hiroyuki wrote:
> >> On Tue, 12 Jan 2010 10:33:08 +0800
> >> Wu Fengguang <fengguang.wu@intel.com> wrote:
> >>
> >> > Sure, here it is :)
> >> > ---
> >> > x86: use the generic page_is_ram()
> >> >
> >> > The generic resource based page_is_ram() works better with memory
> >> > hotplug/hotremove. So switch the x86 e820map based code to it.
> >> >
> >> > CC: Andi Kleen <andi@firstfloor.org>
> >> > CC: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> >> > Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
> >>
> >> Ack.
> >
> > Thank you.
> >
> >>
> >> > +#ifdef CONFIG_X86
> >> > + A /*
> >> > + A A * A special case is the first 4Kb of memory;
> >> > + A A * This is a BIOS owned area, not kernel ram, but generally
> >> > + A A * not listed as such in the E820 table.
> >> > + A A */
> >> > + A if (pfn == 0)
> >> > + A A A A A return 0;
> >> > +
> >> > + A /*
> >> > + A A * Second special case: Some BIOSen report the PC BIOS
> >> > + A A * area (640->1Mb) as ram even though it is not.
> >> > + A A */
> >> > + A if (pfn >= (BIOS_BEGIN >> PAGE_SHIFT) &&
> >> > + A A A pfn < A (BIOS_END A >> PAGE_SHIFT))
> >> > + A A A A A return 0;
> >> > +#endif
> >>
> >> I'm glad if this part is sorted out in clean way ;)
> >
> > Two possible solutions are:
> >
> > - to exclude the above two ranges directly in e820 map;
> > - to not add the above two ranges into iomem_resource.
> >
> > Yinghai, do you have any suggestions?
> > We want to get rid of the two explicit tests from page_is_ram().
>
> please check attached patch.
>
> YH
Thank you, it works!
Content-Description: remove_bios_begin_end.patch
> [PATCH] x86: remove bios data range from e820
>
> to prepare move page_is_ram as generic one
>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org.
Malformed email address..
> ---
> arch/x86/kernel/e820.c | 8 ++++++++
> arch/x86/kernel/head32.c | 2 --
> arch/x86/kernel/head64.c | 2 --
> arch/x86/kernel/setup.c | 19 ++++++++++++++++++-
> arch/x86/mm/ioremap.c | 16 ----------------
> 5 files changed, 26 insertions(+), 21 deletions(-)
>
> Index: linux-2.6/arch/x86/kernel/setup.c
> ===================================================================
> --- linux-2.6.orig/arch/x86/kernel/setup.c
> +++ linux-2.6/arch/x86/kernel/setup.c
> @@ -657,6 +657,23 @@ static struct dmi_system_id __initdata b
> {}
> };
>
> +static void __init trim_bios_range(void)
How about e820_trim_bios_range() ?
> +{
> + /*
> + * A special case is the first 4Kb of memory;
> + * This is a BIOS owned area, not kernel ram, but generally
> + * not listed as such in the E820 table.
> + */
> + e820_update_range(0, PAGE_SIZE, E820_RAM, E820_RESERVED);
> + /*
> + * special case: Some BIOSen report the PC BIOS
> + * area (640->1Mb) as ram even though it is not.
> + * take them out.
> + */
> + e820_remove_range(BIOS_BEGIN, BIOS_END - BIOS_BEGIN, E820_RAM, 1);
> + sanitize_e820_map(e820.map, ARRAY_SIZE(e820.map), &e820.nr_map);
> +}
> +
> Index: linux-2.6/arch/x86/kernel/head32.c
> ===================================================================
> --- linux-2.6.orig/arch/x86/kernel/head32.c
> +++ linux-2.6/arch/x86/kernel/head32.c
> @@ -29,8 +29,6 @@ static void __init i386_default_early_se
>
> void __init i386_start_kernel(void)
> {
> - reserve_early_overlap_ok(0, PAGE_SIZE, "BIOS data page");
> -
> #ifdef CONFIG_X86_TRAMPOLINE
> /*
> * But first pinch a few for the stack/trampoline stuff
> Index: linux-2.6/arch/x86/kernel/head64.c
> ===================================================================
> --- linux-2.6.orig/arch/x86/kernel/head64.c
> +++ linux-2.6/arch/x86/kernel/head64.c
> @@ -98,8 +98,6 @@ void __init x86_64_start_reservations(ch
> {
> copy_bootdata(__va(real_mode_data));
>
> - reserve_early_overlap_ok(0, PAGE_SIZE, "BIOS data page");
> -
> reserve_early(__pa_symbol(&_text), __pa_symbol(&__bss_stop), "TEXT DATA BSS");
>
> #ifdef CONFIG_BLK_DEV_INITRD
The above two trunks don't apply in latest linux-next.
Not a big problem for my test though.
Thanks,
Fengguang
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-01-13 2:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 3:32 [PATCH - resend] Memory-Hotplug: Fix the bug on interface /dev/mem for 64-bit kernel(v1) Zheng, Shaohui
2010-01-08 5:02 ` H. Peter Anvin
2010-01-08 5:18 ` Zheng, Shaohui
2010-01-08 19:47 ` Andi Kleen
2010-01-12 0:58 ` KAMEZAWA Hiroyuki
2010-01-08 12:48 ` Wu Fengguang
2010-01-11 2:20 ` Zheng, Shaohui
2010-01-11 12:43 ` Wu Fengguang
2010-01-12 0:30 ` KAMEZAWA Hiroyuki
2010-01-12 1:38 ` Andi Kleen
2010-01-12 1:39 ` KAMEZAWA Hiroyuki
2010-01-12 1:50 ` KAMEZAWA Hiroyuki
2010-01-12 2:45 ` Wu Fengguang
2010-01-12 2:33 ` Wu Fengguang
2010-01-12 2:39 ` KAMEZAWA Hiroyuki
2010-01-12 13:35 ` Wu Fengguang
2010-01-12 23:01 ` Yinghai Lu
2010-01-13 2:29 ` Wu Fengguang [this message]
2010-01-12 5:45 ` Zheng, Shaohui
2010-01-12 5:51 ` Zheng, Shaohui
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=20100113022948.GD10184@localhost \
--to=fengguang.wu@intel.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=haveblue@us.ibm.com \
--cc=hpa@zytor.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=shaohui.zheng@intel.com \
--cc=x86@kernel.org \
--cc=y-goto@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).