[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160630143431.GA2818@dhcp-128-65.nay.redhat.com>
Date: Thu, 30 Jun 2016 10:34:31 -0400
From: Dave Young <dyoung@...hat.com>
To: Matt Fleming <matt@...eblueprint.co.uk>
Cc: Ard Biesheuvel <ard.biesheuvel@...aro.org>,
linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org,
Andy Lutomirski <luto@...capital.net>,
Borislav Petkov <bp@...en8.de>,
Josh Boyer <jwboyer@...oraproject.org>,
Josh Triplett <josh@...htriplett.org>,
Kamezawa Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Leif Lindholm <leif.lindholm@...aro.org>,
Mark Rutland <mark.rutland@....com>,
Môshe van der Sterre <me@...he.nl>,
Peter Jones <pjones@...hat.com>,
Taku Izumi <izumi.taku@...fujitsu.com>,
Tony Luck <tony.luck@...el.com>,
Xishi Qiu <qiuxishi@...wei.com>
Subject: Re: [PATCH 00/11] efi: Permanent runtime EFI memmap support
Hi, Matt
On 06/23/16 at 12:34pm, Matt Fleming wrote:
> This series adds support for keeping the EFI memory map around at
> runtime for x86 (ARM and arm64 already have this support).
>
> Additionally, drivers can now reserve EFI boot services regions such
> that they are not released back to the kernel during
> efi_free_boot_services().
>
> With these two features it becomes possible to pass things like the
> EFI System Resource Table data structures across kexec reboot.
>
> This series also includes a whole bunch of refactoring and cleanups to
> move code out of arch or driver-specific files into generic places.
>
> I've given these patches some light testing, but it would be good if
> others could provide more given that this series touches so many
> different code paths.
Tested kexec/kdump and the bgrt reservation with kexec and kexec_file
system call. But due to a crypto issue I can not test signature
verification of kexec_file, but I think that is a separate problem.
For these parts:
Tested-by: Dave Young <dyoung@...hat.com>
Thanks
Dave
Powered by blists - more mailing lists