From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Yinghai <yinghai@kernel.org>
Cc: Florian Fainelli <ffainelli@freebox.fr>,
"sodaville@linutronix.de" <sodaville@linutronix.de>,
Ingo Molnar <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [sodaville] [PATCH] x86/trampoline: fallback to fixed trampoline address if no e820 map is provided
Date: Thu, 23 Dec 2010 10:51:56 -0800 [thread overview]
Message-ID: <4D139A4C.7000003@linux.intel.com> (raw)
In-Reply-To: <7A03AE18-9737-41D6-8EF5-6C6C29C1BF0D@kernel.org>
On 12/23/2010 05:16 AM, Yinghai wrote:
>
> On Dec 23, 2010, at 1:57 AM, Florian Fainelli <ffainelli@freebox.fr> wrote:
>
>> On Tuesday 14 December 2010 22:19:39 Florian Fainelli wrote:
>>> From: Florian Fainelli <ffainelli@freebox.fr>
>>>
>>> Since 893f38d1 (x86: Use find_e820() instead of hard coded trampoline
>>> address), the trampoline base address should be provided by the BIOS as an
>>> e820 area. Some minimalistic BIOSes (like CEFDK on CE4100) may not provide
>>> any e820 area, still we should fallback to a fixed trampoline base address
>>> for SMP to work correctly.
>
> No e820 memmap ?
>
> Not sure how does it work
>
> Do you have boot log with debug ?
>
> Also recent kernel is using memblock already for finding free area.
>
OK, this deeply troubles me. This is clearly not the right approach
here... the memory map should be fed to the kernel, this has been a
requirement all along, and Linus has very deliberately not agreed to
exceptions (and I agree with that stance.)
So this patch is a non-starter... I presume the memory map is being
provided in through the device (which means it should be fed into
memblock in current kernels, although the ordering may need to be tweaked?)
-hpa
prev parent reply other threads:[~2010-12-23 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 21:19 [PATCH] x86/trampoline: fallback to fixed trampoline address if no e820 map is provided Florian Fainelli
2010-12-23 9:57 ` Florian Fainelli
2010-12-23 13:16 ` Yinghai
2010-12-23 13:20 ` Florian Fainelli
2010-12-23 17:46 ` Yinghai
2010-12-23 18:51 ` H. Peter Anvin [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=4D139A4C.7000003@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=ffainelli@freebox.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sodaville@linutronix.de \
--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