From: Dave Young <dyoung@redhat.com>
To: Matt Fleming <matt@codeblueprint.co.uk>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
dyoung@redhat.com, x86@kernel.org,
Nicolai Stange <nicstange@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
hpa@zytor.com, Dan Williams <dan.j.williams@intel.com>,
mika.penttila@nextfour.com, bhsharma@redhat.com
Subject: [PATCH V2 0/4] efi/x86: move efi bgrt init code to early init
Date: Mon, 16 Jan 2017 10:45:54 +0800 [thread overview]
Message-ID: <20170116024554.461236678@redhat.com> (raw)
Hi,
Here the the update of the series for moving bgrt init code to early init.
Main changes is:
- Move the 1st patch to the last because it does not block the 2nd patch
any more with Peter's patch to prune invlid memmap entries:
https://git.kernel.org/cgit/linux/kernel/git/efi/efi.git/commit/?h=next&id=b2a91
a35445229
But it is still tood to have since efi_mem_reserve only cares about boot related
mem ranges.
- Other comments about code itself, details please the the patches themselves.
arch/x86/include/asm/efi.h | 1
arch/x86/kernel/acpi/boot.c | 12 +++++++
arch/x86/platform/efi/efi-bgrt.c | 59 ++++++++++++++++-----------------------
arch/x86/platform/efi/efi.c | 26 +++--------------
arch/x86/platform/efi/quirks.c | 2 -
drivers/acpi/bgrt.c | 28 +++++++++++++-----
drivers/firmware/efi/fake_mem.c | 3 +
drivers/firmware/efi/memmap.c | 22 +++++++++++++-
include/linux/efi-bgrt.h | 7 +---
include/linux/efi.h | 5 +--
init/main.c | 1
11 files changed, 92 insertions(+), 74 deletions(-)
Thanks
Dave
next reply other threads:[~2017-01-16 2:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 2:45 Dave Young [this message]
2017-01-16 2:45 ` [PATCH V2 1/4] efi/x86: move efi bgrt init code to early init code Dave Young
2017-01-17 10:39 ` Nicolai Stange
2017-01-17 17:10 ` Ard Biesheuvel
2017-01-18 2:16 ` Dave Young
2017-01-18 13:48 ` [PATCH V3 " Dave Young
2017-01-18 14:00 ` Ard Biesheuvel
2017-01-18 19:24 ` Bhupesh Sharma
2017-01-19 12:48 ` Ard Biesheuvel
2017-01-26 3:39 ` Dave Young
2017-01-16 2:45 ` [PATCH V2 2/4] efi/x86: move efi_print_memmap to drivers/firmware/efi/memmap.c Dave Young
2017-01-17 10:39 ` Nicolai Stange
2017-01-17 17:11 ` Ard Biesheuvel
2017-01-16 2:45 ` [PATCH V2 3/4] efi/x86: add debug code to print cooked memmap Dave Young
2017-01-17 10:39 ` Nicolai Stange
2017-01-16 2:45 ` [PATCH V2 4/4] efi/x86: make efi_memmap_reserve only insert into boot mem areas Dave Young
2017-01-17 10:40 ` Nicolai Stange
2017-01-17 17:13 ` Ard Biesheuvel
2017-01-17 19:48 ` Nicolai Stange
2017-01-18 11:01 ` Dave Young
2017-01-18 11:06 ` Dave Young
2017-01-18 13:33 ` Dave Young
2017-01-18 2:28 ` Dave Young
2017-01-27 17:03 ` [PATCH V2 0/4] efi/x86: move efi bgrt init code to early init Ard Biesheuvel
2017-02-03 7:12 ` Dave Young
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=20170116024554.461236678@redhat.com \
--to=dyoung@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bhsharma@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mika.penttila@nextfour.com \
--cc=mingo@kernel.org \
--cc=nicstange@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).