From: "Huang, Ying" <ying.huang@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: use add_highpages_with_active_regions for high pages init
Date: Mon, 16 Jun 2008 13:45:26 +0800 [thread overview]
Message-ID: <1213595126.10376.27.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <4855FC70.9050900@zytor.com>
On Sun, 2008-06-15 at 22:38 -0700, H. Peter Anvin wrote:
> Huang, Ying wrote:
> > On Sun, 2008-06-15 at 20:46 -0700, Yinghai Lu wrote:
> > [...]
> >> don't need,
> >> EFI memmap should be reserved in e820map, so it should not show up in
> >> early_node_map.
> >
> > I don't think so. EFI memmap comes from boot-loader not from BIOS. It
> > contains boot-loader execution information (such as EfiLoaderCode,
> > EfiLoaderData, etc), and it will be located at different position for
> > each system reboot.
> >
> > If it is reserved in E820 memmap, hibernation can not work. Because the
> > memory area for EFI memmap is not E820 RAM, it is not saved during
> > hibernating and restored after restoring from disk.
> >
> > Linked list of struct setup_data has similar requirement too.
> >
>
> That doesn't mean we can't use the E820 memory map structure for it. We
> just have to define a new kernel-internal memory type, instead of using
> type 2 (reserved).
Yes. I will do this.
Best Regards,
Huang Ying
next prev parent reply other threads:[~2008-06-16 5:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 3:05 [PATCH] x86: replace shrink pages with remove_active_ranges v2 Yinghai Lu
2008-06-14 3:07 ` [PATCH] x86: cleanup reloated_initrd Yinghai Lu
2008-06-14 8:28 ` Ingo Molnar
2008-06-14 18:41 ` H. Peter Anvin
2008-06-14 19:27 ` Yinghai Lu
2008-06-14 19:39 ` H. Peter Anvin
2008-06-14 22:08 ` Yinghai Lu
2008-06-14 6:23 ` [PATCH] x86: replace shrink pages with remove_active_ranges v2 Ingo Molnar
2008-06-14 7:56 ` [PATCH] x86: use add_highpages_with_active_regions for high pages init Yinghai Lu
2008-06-14 8:23 ` Ingo Molnar
2008-06-14 8:50 ` Ingo Molnar
2008-06-14 8:59 ` Ingo Molnar
2008-06-14 9:05 ` Yinghai Lu
2008-06-16 1:20 ` Huang, Ying
2008-06-16 3:46 ` Yinghai Lu
2008-06-16 4:39 ` Yinghai Lu
2008-06-16 5:37 ` Huang, Ying
2008-06-16 5:38 ` H. Peter Anvin
2008-06-16 5:43 ` Yinghai Lu
2008-06-16 5:45 ` Huang, Ying [this message]
2008-06-15 1:32 ` [PATCH] x86: use add_highpages_with_active_regions for high pages init v2 Yinghai Lu
2008-06-16 8:09 ` Ingo Molnar
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=1213595126.10376.27.camel@caritas-dev.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.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