From: Huang Ying <ying.huang@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Cliff Wickman <cpw@sgi.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"yinghai@kernel.org" <yinghai@kernel.org>
Subject: Re: [PATCH] x86: efi/e820 table merge fix
Date: Wed, 17 Jun 2009 09:44:59 +0800 [thread overview]
Message-ID: <1245203099.11965.7.camel@yhuang-dev.sh.intel.com> (raw)
In-Reply-To: <4A384914.1090900@zytor.com>
On Wed, 2009-06-17 at 09:38 +0800, H. Peter Anvin wrote:
> Huang Ying wrote:
> > On Wed, 2009-06-17 at 05:43 +0800, Cliff Wickman wrote:
> >> From: Cliff Wickman <cpw@sgi.com>
> >> --- linux.orig/arch/x86/kernel/efi.c
> >> +++ linux/arch/x86/kernel/efi.c
> >> @@ -240,10 +240,35 @@ static void __init do_add_efi_memmap(voi
> >> unsigned long long size = md->num_pages << EFI_PAGE_SHIFT;
> >> int e820_type;
> >>
> >> - if (md->attribute & EFI_MEMORY_WB)
> >> - e820_type = E820_RAM;
> >> - else
> >> + switch (md->type) {
> >> + case EFI_LOADER_CODE:
> >> + case EFI_LOADER_DATA:
> >> + case EFI_BOOT_SERVICES_CODE:
> >> + case EFI_BOOT_SERVICES_DATA:
> >> + case EFI_CONVENTIONAL_MEMORY:
> >> + if (md->attribute & EFI_MEMORY_WB)
> >> + e820_type = E820_RAM;
> >> + else
> >> + e820_type = E820_RESERVED;
> >> + break;
> >
> > Why does BIOS mark memory region without EFI_MEMORY_WB as these types?
> > Any example?
> >
> Probably not, but if it does, it's broken, and the memory should be
> ignored. The original code had the EFI_MEMORY_WB check already, so it
> seems prudent to keep it.
Maybe we need a real life example for that "fix". And attribute that to
the vendor in comments.
Best Regards,
Huang Ying
next prev parent reply other threads:[~2009-06-17 1:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 21:43 Cliff Wickman
2009-06-17 1:10 ` Huang Ying
2009-06-17 1:38 ` H. Peter Anvin
2009-06-17 1:44 ` Huang Ying [this message]
2009-06-17 4:03 ` H. Peter Anvin
2009-06-17 5:08 ` Huang Ying
2009-06-17 14:58 ` Cliff Wickman
2009-06-17 18:28 ` H. Peter Anvin
2009-06-17 18:30 ` H. Peter Anvin
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=1245203099.11965.7.camel@yhuang-dev.sh.intel.com \
--to=ying.huang@intel.com \
--cc=cpw@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
Powered by JetHome