From: Ingo Molnar <mingo@elte.hu>
To: Paul Jackson <pj@sgi.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Yinghai Lu <yhlu.kernel@gmail.com>,
Jack Steiner <steiner@sgi.com>, Mike Travis <travis@sgi.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, "Huang,
Ying" <ying.huang@intel.com>, Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH 2/2] x86 boot: only pick up additional EFI memmap if add_efi_memmap flag
Date: Wed, 25 Jun 2008 18:11:01 +0200 [thread overview]
Message-ID: <20080625161101.GD24967@elte.hu> (raw)
In-Reply-To: <20080625124446.25036.25226.sendpatchset@polaris-admin.engr.sgi.com>
* Paul Jackson <pj@sgi.com> wrote:
> From: Paul Jackson <pj@sgi.com>
>
> Applies on top of the previous patch:
> x86 boot: add code to add BIOS provided EFI memory entries to kernel
>
> Instead of always adding EFI memory map entries (if present) to the
> memory map after initially finding either E820 BIOS memory map entries
> and/or kernel command line memmap entries, -instead- only add such
> additional EFI memory map entries if the kernel boot option:
>
> add_efi_memmap
>
> is specified.
>
> Requiring this 'add_efi_memmap' option is backward compatible with
> kernels that didn't load such additional EFI memory map entries in the
> first place, and it doesn't override a configuration that tries to
> replace all E820 or EFI BIOS memory map entries with ones given
> entirely on the kernel command line.
applied to tip/x86/setup-memory - thanks Paul.
Ingo
prev parent reply other threads:[~2008-06-25 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 12:44 [PATCH 1/2] x86 boot: more tweaks to hex prints of some pfn addresses Paul Jackson
2008-06-25 12:44 ` [PATCH 2/2] x86 boot: only pick up additional EFI memmap if add_efi_memmap flag Paul Jackson
2008-06-25 16:11 ` Ingo Molnar [this message]
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=20080625161101.GD24967@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--cc=x86@kernel.org \
--cc=yhlu.kernel@gmail.com \
--cc=ying.huang@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
Powered by JetHome