From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Jerry Hoemann <jerry.hoemann@hp.com>
Cc: rob@landley.net, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, x86@kernel.org, matt.fleming@intel.com,
yinghai@kernel.org, akpm@linux-foundation.org, bp@suse.de,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-efi@vger.kernel.org, penberg@kernel.org,
mingo.kernel.org@gmail.com, vgoyal@redhat.com
Subject: Re: [RFC v2 0/2] Early use of boot service memory
Date: Thu, 21 Nov 2013 23:07:44 +0000 [thread overview]
Message-ID: <20131121230744.GA31592@srcf.ucam.org> (raw)
In-Reply-To: <1385067686-73500-1-git-send-email-jerry.hoemann@hp.com>
On Thu, Nov 21, 2013 at 02:01:24PM -0700, Jerry Hoemann wrote:
>
> Some platform have firmware that violates the UEFI spec and access boot
> service code or data segments after the system has called ExitBootServices().
> The call to efi_reserve_boot_services in setup_arch is a workaround to
> avoid using boot service memory until after the kernel has done
> SetVirtualAddressMap. However, this reservation fragments memory
> which can cause large allocations early in boot (e.g. crash kernel)
> to fail.
This is a problem we have to solve, but I don't think this is the right
way to solve it. Why do we not just reattempt to perform the allocation
immediately after we've freed the boot services regions?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2013-11-21 23:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 21:01 [RFC v2 0/2] Early use of boot service memory Jerry Hoemann
2013-11-21 21:01 ` [RFC v2 1/2] efi: " Jerry Hoemann
2013-11-21 21:01 ` [RFC v2 2/2] x86, " Jerry Hoemann
2013-11-21 22:19 ` Borislav Petkov
2013-11-21 23:07 ` Matthew Garrett [this message]
2013-11-21 23:18 ` [RFC v2 0/2] " H. Peter Anvin
2013-11-21 23:37 ` Matthew Garrett
2013-11-22 1:12 ` H. Peter Anvin
2013-11-22 1:25 ` jerry.hoemann
2013-11-22 1:29 ` Yinghai Lu
2013-11-22 1:31 ` H. Peter Anvin
2013-11-22 2:34 ` Vivek Goyal
2013-11-22 2:42 ` H. Peter Anvin
2013-11-22 2:29 ` Vivek Goyal
2013-11-22 3:32 ` HATAYAMA Daisuke
2013-11-22 2:32 ` Vivek Goyal
2013-11-21 23:31 ` jerry.hoemann
2013-11-21 23:38 ` Matthew Garrett
2013-11-22 1:05 ` jerry.hoemann
2013-11-22 1:16 ` Matthew Garrett
2013-12-16 18:43 ` jerry.hoemann
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=20131121230744.GA31592@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=jerry.hoemann@hp.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo.kernel.org@gmail.com \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=rob@landley.net \
--cc=tglx@linutronix.de \
--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