linux-kernel - [PATCH 0/3] Find mirrored memory, use for boot time allocations

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 4 May 2015 13:52:23 -0700
From:	Tony Luck <tony.luck@...el.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: [PATCH 0/3] Find mirrored memory, use for boot time allocations

UEFI published the spec that descibes the attribute bit we need to
find out which memory ranges are mirrored. So time to post the real
version of this series.

These patches are against 4.1-rc1 ... I think there are a couple of
trivial conflicts with the current mmotm.

Tony Luck (3):
  mm/memblock: Add extra "flag" to memblock to allow selection of memory
    based on attribute
  mm/memblock: Allocate boot time data structures from mirrored memory
  x86, mirror: x86 enabling - find mirrored memory ranges

 arch/s390/kernel/crash_dump.c |   4 +-
 arch/sparc/mm/init_64.c       |   4 +-
 arch/x86/kernel/check.c       |   2 +-
 arch/x86/kernel/e820.c        |   2 +-
 arch/x86/kernel/setup.c       |   3 ++
 arch/x86/mm/init_32.c         |   2 +-
 arch/x86/platform/efi/efi.c   |  21 ++++++++
 include/linux/efi.h           |   3 ++
 include/linux/memblock.h      |  43 ++++++++++------
 mm/cma.c                      |   4 +-
 mm/memblock.c                 | 113 ++++++++++++++++++++++++++++++++----------
 mm/memtest.c                  |   2 +-
 mm/nobootmem.c                |  12 ++++-
 13 files changed, 162 insertions(+), 53 deletions(-)

-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/