From: Jacob Shin <jacob.shin@amd.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: X86-ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>, Tejun Heo <tj@kernel.org>,
Dave Young <dyoung@redhat.com>, Chao Wang <chaowang@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>,
Andreas Herrmann <andreas.herrmann3@amd.com>,
Borislav Petkov <borislav.petkov@amd.com>
Subject: Re: [PATCH 5/5] x86: if kernel .text .data .bss are not marked as E820_RAM, complain and fix
Date: Fri, 24 Aug 2012 23:25:48 -0500 [thread overview]
Message-ID: <20120825042541.GE26127@jshin-Toonie> (raw)
In-Reply-To: <CAE9FiQXhtEEyGnd1sHjcSDHiC6ZQ77rQDo-nSCHpjcjvMCzPDg@mail.gmail.com>
On Fri, Aug 24, 2012 at 06:23:48PM -0700, Yinghai Lu wrote:
> On Fri, Aug 24, 2012 at 4:55 PM, Jacob Shin <jacob.shin@amd.com> wrote:
> > There could be cases where user supplied memmap=exactmap memory
> > mappings do not mark the region where the kernel .text .data and
> > .bss reside as E820_RAM as reported here:
> >
> > https://lkml.org/lkml/2012/8/14/86
> >
> > Handle it by complaining, and adding the range back into the e820.
> >
> > Signed-off-by: Jacob Shin <jacob.shin@amd.com>
> > ---
> > arch/x86/kernel/setup.c | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
> >
> > diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
> > index 4217fb4..b84aceb5 100644
> > --- a/arch/x86/kernel/setup.c
> > +++ b/arch/x86/kernel/setup.c
> > @@ -926,6 +926,21 @@ void __init setup_arch(char **cmdline_p)
> > insert_resource(&iomem_resource, &data_resource);
> > insert_resource(&iomem_resource, &bss_resource);
> >
> > + /*
> > + * Complain if .text .data and .bss are not marked as E820_RAM and
> > + * attempt to fix it by adding the range. We may have a confused BIOS,
> > + * or the user may have incorrectly supplied it via memmap=exactmap. If
> > + * we really are running on top non-RAM, we will crash later anyways.
> > + */
> > + if (!e820_all_mapped(code_resource.start, bss_resource.end, E820_RAM)) {
> > + pr_warn(".text .data .bss are not marked as E820_RAM!\n");
> > +
> > + e820_add_region(code_resource.start,
> > + bss_resource.end - code_resource.start + 1,
> > + E820_RAM);
> > + sanitize_e820_map(e820.map, ARRAY_SIZE(e820.map), &e820.nr_map);
>
> this sanitze_e820_map could be spared. trim_bios_range will
> that always.
Ah. okay
>
> > + }
> > +
> > trim_bios_range();
> > #ifdef CONFIG_X86_32
> > if (ppro_with_ram_bug()) {
>
> also should use brk_limit instead of bss_resource.end. aka need to
> keep the map for brk area.
Okay.. will fix on Monday
>
> Thanks
>
> Yinghai
>
prev parent reply other threads:[~2012-08-25 4:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 23:55 [PATCH V4 0/5] x86: Create direct mappings for E820_RAM only Jacob Shin
2012-08-24 23:55 ` [PATCH 1/5] x86: Move enabling of PSE and PGE out of init_memory_mapping Jacob Shin
2012-08-25 1:25 ` Yinghai Lu
2012-08-25 1:49 ` Yinghai Lu
2012-08-25 2:06 ` Yinghai Lu
2012-08-25 4:15 ` Jacob Shin
2012-08-25 4:13 ` Jacob Shin
2012-08-24 23:55 ` [PATCH 2/5] x86: find_early_table_space based on memory ranges that are being mapped Jacob Shin
2012-10-21 21:22 ` Tom Rini
2012-08-24 23:55 ` [PATCH 3/5] x86: Only direct map addresses that are marked as E820_RAM Jacob Shin
2012-08-25 0:17 ` Jacob Shin
2012-08-25 0:30 ` H. Peter Anvin
2012-08-25 0:49 ` Jacob Shin
2012-08-25 1:13 ` H. Peter Anvin
2012-08-25 4:20 ` Jacob Shin
2012-08-25 4:21 ` H. Peter Anvin
2012-08-27 19:17 ` Jacob Shin
2012-08-27 20:15 ` H. Peter Anvin
2012-08-25 1:07 ` Yinghai Lu
2012-08-25 4:24 ` Jacob Shin
2012-08-25 4:54 ` Yinghai Lu
2012-08-27 18:49 ` Jacob Shin
2012-08-27 20:16 ` H. Peter Anvin
2012-08-28 16:06 ` Jacob Shin
2012-08-28 16:11 ` H. Peter Anvin
2012-08-24 23:55 ` [PATCH 4/5] x86: Fixup code testing if a pfn is direct mapped Jacob Shin
2012-08-24 23:55 ` [PATCH 5/5] x86: if kernel .text .data .bss are not marked as E820_RAM, complain and fix Jacob Shin
2012-08-25 1:23 ` Yinghai Lu
2012-08-25 4:25 ` Jacob Shin [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=20120825042541.GE26127@jshin-Toonie \
--to=jacob.shin@amd.com \
--cc=andreas.herrmann3@amd.com \
--cc=borislav.petkov@amd.com \
--cc=chaowang@redhat.com \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=vgoyal@redhat.com \
--cc=x86@kernel.org \
--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
all inboxes | Powered by JetHome®