[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOJsxLEoN2uYR9V3bowv2O7F8L5t+kVrdehHW151cEcfgx-oJg@mail.gmail.com>
Date: Tue, 12 Nov 2013 12:37:29 +0200
From: Pekka Enberg <penberg@...nel.org>
To: Jerry Hoemann <jerry.hoemann@...com>
Cc: Rob Landley <rob@...dley.net>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86 maintainers <x86@...nel.org>,
Matt Fleming <matt.fleming@...el.com>,
Yinghai Lu <yinghai@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"list@...ederm.org:DOCUMENTATION <linux-doc@...r.kernel.org>,
list@...ederm.org:MEMORY MANAGEMENT <linux-mm@...ck.org>,"
<linux-doc@...r.kernel.org>, linux-efi@...r.kernel.org,
Vivek Goyal <vgoyal@...hat.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] Early use of boot service memory
On Tue, Nov 12, 2013 at 4:15 AM, Jerry Hoemann <jerry.hoemann@...com> wrote:
> Some platform have firmware that violates UEFI spec and access boot service
> code or data segments after the system has called Exit Boot Services.
> The call to efi_reserve_boot_services in setup_arch is a work around to
> avoid using boot service memory until after the kernel has done
> Set Virtual Map.
>
> However, this reservation fragments memory which can cause
> large allocations early in boot (e.g. crash kernel) to fail.
What is the exact problem you're trying to solve here? How will the
problem be fixed for platforms that break the UEFI specification?
Pekka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists