From mboxrd@z Thu Jan 1 00:00:00 1970 From: jerry.hoemann-VXdhtT5mjnY@public.gmane.org Subject: Re: [RFC v2 0/2] Early use of boot service memory Date: Thu, 21 Nov 2013 16:31:04 -0700 Message-ID: <20131121233104.GF1106@anatevka.fc.hp.com> References: <1385067686-73500-1-git-send-email-jerry.hoemann@hp.com> <20131121230744.GA31592@srcf.ucam.org> Reply-To: jerry.hoemann-VXdhtT5mjnY@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20131121230744.GA31592-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org> Sender: linux-efi-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Matthew Garrett Cc: rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org, tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org, mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org, x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org, yinghai-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org, bp-l3A5Bk7waGM@public.gmane.org, linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, penberg-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, mingo.kernel.org-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org List-Id: linux-efi@vger.kernel.org On Thu, Nov 21, 2013 at 11:07:44PM +0000, Matthew Garrett wrote: > 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? Hi Matthew, I tried this back on 3.11 kernel and reserve_crashkernel after free of boot services failed. I will admit to not digging in too deeply as to why it failed. My earlier email: https://lkml.org/lkml/2013/9/18/457 thanks > > -- > Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org -- ---------------------------------------------------------------------------- Jerry Hoemann Software Engineer Hewlett-Packard 3404 E Harmony Rd. MS 57 phone: (970) 898-1022 Ft. Collins, CO 80528 FAX: (970) 898-XXXX email: jerry.hoemann-VXdhtT5mjnY@public.gmane.org ----------------------------------------------------------------------------