From: Matt Fleming <matt@console-pimps.org>
To: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] EFI urgent fixes
Date: Wed, 4 Jun 2014 17:53:58 +0100 [thread overview]
Message-ID: <20140604164955.GA3059@console-pimps.org> (raw)
Folks,
Here are two commits I've queued up from Dave. The first fixes the efi
earlyprintk code and the second fixes a bug where we were exporting the
EFI runtime mappings for use by kexec-tools, despite the fact that those
mappings were not persistent across kexec reboot.
The following changes since commit 47514c996fac5e6f13ef3a4c5e23f1c5cffabb7b:
efi: Pass correct file handle to efi_file_{read,close} (2014-04-10 21:20:03 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git tags/efi-urgent
for you to fetch changes up to a3530e8fe980f756b823d451fe9243f26db95fa5:
x86/efi: Do not export efi runtime map in case old map (2014-06-02 12:21:59 +0100)
----------------------------------------------------------------
* Fix earlyprintk=efi,keep support by switching to an ioremap() mapping
of the framebuffer when early_ioremap() is no longer available and
dropping __init from functions that may be invoked after
free_initmem() - Dave Young
* We shouldn't be exporting the EFI runtime map in sysfs if not using
the new 1:1 EFI mapping code since in that case the mappings are not
static across a kexec reboot - Dave Young
----------------------------------------------------------------
Dave Young (2):
x86/efi: earlyprintk=efi,keep fix
x86/efi: Do not export efi runtime map in case old map
arch/x86/platform/efi/early_printk.c | 83 +++++++++++++++++++++++++++---------
arch/x86/platform/efi/efi.c | 3 ++
2 files changed, 67 insertions(+), 19 deletions(-)
--
Matt Fleming, Intel Open Source Technology Center
next reply other threads:[~2014-06-04 16:54 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 16:53 Matt Fleming [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-30 21:06 [GIT PULL] EFI urgent fixes Matt Fleming
2015-07-31 7:56 ` Ingo Molnar
2015-05-05 16:27 Matt Fleming
2015-05-06 6:31 ` Ingo Molnar
2015-03-02 12:51 Matt Fleming
2015-03-02 13:24 ` Ingo Molnar
2015-03-02 13:35 ` Matt Fleming
2015-02-18 11:55 Matt Fleming
2015-02-18 13:43 ` Ingo Molnar
2015-02-18 16:36 ` Ard Biesheuvel
2015-02-18 16:57 ` Ingo Molnar
2014-09-25 7:31 Matt Fleming
2014-09-25 14:41 ` Ingo Molnar
2014-09-25 14:44 ` Matt Fleming
2014-09-26 11:27 ` Paul Bolle
2014-09-26 11:35 ` Ingo Molnar
2014-09-26 12:24 ` Matt Fleming
2014-09-27 5:49 ` Ingo Molnar
2014-09-26 11:44 ` Matt Fleming
2014-09-26 11:59 ` Paul Bolle
2014-09-26 12:34 ` Matt Fleming
2014-09-26 12:55 ` Paul Bolle
2014-09-27 8:04 ` Valentin Rothberg
2014-09-27 9:59 ` Paul Bolle
2014-09-08 21:55 Matt Fleming
2014-09-09 5:07 ` Ingo Molnar
2014-09-09 7:07 ` Matt Fleming
2014-09-09 14:55 ` Ingo Molnar
2014-08-22 7:52 Matt Fleming
2014-08-22 8:15 ` Ingo Molnar
2014-07-14 12:54 Matt Fleming
2014-06-27 14:51 Matt Fleming
2014-04-11 7:16 Matt Fleming
2014-04-11 8:27 ` Ingo Molnar
2014-02-14 13:08 Matt Fleming
2013-11-29 12:09 Matt Fleming
2013-07-11 11:16 Matt Fleming
2013-06-07 11:50 Matt Fleming
2013-06-10 21:36 ` Matt Fleming
2013-05-17 10:18 Matt Fleming
2013-04-25 8:49 Matt Fleming
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=20140604164955.GA3059@console-pimps.org \
--to=matt@console-pimps.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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