From: Dave Young <dyoung@redhat.com>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
"Andy Lutomirski" <luto@amacapital.net>,
"Borislav Petkov" <bp@alien8.de>,
"Josh Boyer" <jwboyer@fedoraproject.org>,
"Josh Triplett" <josh@joshtriplett.org>,
"Kamezawa Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
"Leif Lindholm" <leif.lindholm@linaro.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Môshe van der Sterre" <me@moshe.nl>,
"Peter Jones" <pjones@redhat.com>,
"Taku Izumi" <izumi.taku@jp.fujitsu.com>,
"Tony Luck" <tony.luck@intel.com>,
"Xishi Qiu" <qiuxishi@huawei.com>
Subject: Re: [PATCH 00/11] efi: Permanent runtime EFI memmap support
Date: Thu, 30 Jun 2016 10:34:31 -0400 [thread overview]
Message-ID: <20160630143431.GA2818@dhcp-128-65.nay.redhat.com> (raw)
In-Reply-To: <1466681690-5850-1-git-send-email-matt@codeblueprint.co.uk>
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@redhat.com>
Thanks
Dave
prev parent reply other threads:[~2016-06-30 14:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 11:34 Matt Fleming
2016-06-23 11:34 ` [PATCH 01/11] x86/efi: Test for EFI_MEMMAP functionality when iterating EFI memmap Matt Fleming
2016-06-23 11:34 ` [PATCH 02/11] x86/efi: Consolidate region mapping logic Matt Fleming
2016-06-23 14:00 ` Borislav Petkov
2016-06-23 11:34 ` [PATCH 03/11] efi: Refactor efi_memmap_init_early() into arch-neutral code Matt Fleming
2016-06-24 11:44 ` Ard Biesheuvel
2016-07-04 12:19 ` Matt Fleming
2016-07-04 22:24 ` Ard Biesheuvel
2016-06-23 11:34 ` [PATCH 04/11] efi: Add efi_memmap_init_late() for permanent EFI memmap Matt Fleming
2016-06-23 11:34 ` [PATCH 05/11] efi/fake_mem: Refactor main two code chunks into functions Matt Fleming
2016-06-23 11:34 ` [PATCH 06/11] efi: Split out EFI memory map functions into new file Matt Fleming
2016-06-23 11:34 ` [PATCH 07/11] efi: Add efi_memmap_install() for installing new EFI memory maps Matt Fleming
2016-06-23 11:34 ` [PATCH 08/11] efi: Allow drivers to reserve boot services forever Matt Fleming
2016-06-23 11:34 ` [PATCH 09/11] efi/runtime-map: Use efi.memmap directly instead of a copy Matt Fleming
2016-06-23 11:34 ` [PATCH 10/11] efi/esrt: Use efi_mem_reserve() and avoid a kmalloc() Matt Fleming
2016-06-23 11:34 ` [PATCH 11/11] x86/efi-bgrt: Use efi_mem_reserve() to avoid copying image data Matt Fleming
2016-06-30 14:41 ` Josh Triplett
2016-06-30 14:34 ` Dave Young [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=20160630143431.GA2818@dhcp-128-65.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bp@alien8.de \
--cc=izumi.taku@jp.fujitsu.com \
--cc=josh@joshtriplett.org \
--cc=jwboyer@fedoraproject.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=leif.lindholm@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mark.rutland@arm.com \
--cc=matt@codeblueprint.co.uk \
--cc=me@moshe.nl \
--cc=pjones@redhat.com \
--cc=qiuxishi@huawei.com \
--cc=tony.luck@intel.com \
/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
all inboxes | Powered by JetHome®