From: lersek@redhat.com (Laszlo Ersek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] beautify EFI memmap logs
Date: Wed, 3 Sep 2014 13:32:18 +0200 [thread overview]
Message-ID: <1409743943-16934-1-git-send-email-lersek@redhat.com> (raw)
changes in v2:
- explain with examples how the log's appearance changes, in patches 3-5
[Ingo]
v1 blurb:
> It's a pain to analyze EFI memmap logs while debugging, especially to
> verify the memory types (an enum) and the memory attributes (a
> bitmap). This series renders those columns human-readable, and unifies
> their formatting between x86, ia64 and arm64.
Thanks
Laszlo
Laszlo Ersek (5):
efi: add macro for EFI_MEMORY_UCE memory attribute
efi: introduce efi_md_typeattr_format()
x86: efi: format EFI memory type & attrs with efi_md_typeattr_format()
ia64: efi: format EFI memory type & attrs with
efi_md_typeattr_format()
arm64: efi: format EFI memory type & attrs with
efi_md_typeattr_format()
include/linux/efi.h | 8 +++++++
arch/arm64/kernel/efi.c | 26 +++++----------------
arch/ia64/kernel/efi.c | 6 +++--
arch/x86/platform/efi/efi.c | 7 ++++--
drivers/firmware/efi/efi.c | 57 +++++++++++++++++++++++++++++++++++++++++++++
5 files changed, 80 insertions(+), 24 deletions(-)
--
1.8.3.1
next reply other threads:[~2014-09-03 11:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 11:32 Laszlo Ersek [this message]
2014-09-03 11:32 ` [PATCH v2 1/5] efi: add macro for EFI_MEMORY_UCE memory attribute Laszlo Ersek
2014-09-03 11:32 ` [PATCH v2 2/5] efi: introduce efi_md_typeattr_format() Laszlo Ersek
2014-09-03 11:32 ` [PATCH v2 3/5] x86: efi: format EFI memory type & attrs with efi_md_typeattr_format() Laszlo Ersek
2014-09-03 11:32 ` [PATCH v2 4/5] ia64: " Laszlo Ersek
2014-09-03 11:32 ` [PATCH v2 5/5] arm64: " Laszlo Ersek
2014-09-03 13:01 ` [PATCH v2 0/5] beautify EFI memmap logs Ard Biesheuvel
2014-09-03 13:18 ` Matt Fleming
2014-09-03 13:25 ` Laszlo Ersek
2014-09-03 13:24 ` Laszlo Ersek
2014-09-03 13:27 ` Ard Biesheuvel
2014-09-03 13:35 ` 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=1409743943-16934-1-git-send-email-lersek@redhat.com \
--to=lersek@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).