From: Ingo Molnar <mingo@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andy Lutomirski <luto@kernel.org>,
x86@kernel.org, Mario Limonciello <mario_limonciello@dell.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] x86/boot: Reorganize and clean up the BIOS area reservation code
Date: Thu, 21 Jul 2016 11:11:32 +0200 [thread overview]
Message-ID: <20160721091132.GA22986@gmail.com> (raw)
In-Reply-To: <92DA2E2A-BCD9-4198-A983-395A06388688@zytor.com>
* H. Peter Anvin <hpa@zytor.com> wrote:
> We already reserve the first megabyte by default. There is something really
> bizarre about this; the bug report simply doesn't seem to make any sense.
Maybe the first megabyte reservation happens after the SMP trampoline allocation
and hence the EBDA/BIOS reservation matters to our ability to allocate the SMP
trampoline specifically?
Anyway, agreed that we need more information.
Thanks,
Ingo
next prev parent reply other threads:[~2016-07-21 9:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 1:32 [PATCH] x86/ebda: If the EBDA is in lowmem, reserve only 4k for the EBDA Andy Lutomirski
2016-07-21 8:14 ` [PATCH] x86/boot: Reorganize and clean up the BIOS area reservation code Ingo Molnar
2016-07-21 8:29 ` H. Peter Anvin
2016-07-21 9:11 ` Ingo Molnar [this message]
2016-07-21 12:32 ` H. Peter Anvin
2016-07-21 9:14 ` Ingo Molnar
2016-07-21 8:31 ` Ingo Molnar
2016-07-21 14:58 ` Andy Lutomirski
2016-07-21 16:18 ` Ingo Molnar
2016-07-21 21:08 ` Andy Lutomirski
2016-07-21 21:28 ` H. Peter Anvin
2016-07-21 21:48 ` Andy Lutomirski
2016-07-21 22:45 ` Andy Lutomirski
2016-07-22 13:00 ` Matt Fleming
2016-07-23 1:16 ` Linus Torvalds
2016-07-26 0:41 ` Andy Lutomirski
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=20160721091132.GA22986@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mario_limonciello@dell.com \
--cc=mjg59@srcf.ucam.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.