linux-kernel - [PATCH 0/2] Default platform MAAR implementation

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]

Message-ID: <1436543559-26886-1-git-send-email-paul.burton@imgtec.com>
Date:	Fri, 10 Jul 2015 16:52:37 +0100
From:	Paul Burton <paul.burton@...tec.com>
To:	<linux-mips@...ux-mips.org>
CC:	Paul Burton <paul.burton@...tec.com>,
	Paolo Bonzini <pbonzini@...hat.com>,
	"Steven J. Hill" <Steven.Hill@...tec.com>,
	<linux-kernel@...r.kernel.org>,
	James Hogan <james.hogan@...tec.com>,
	Markos Chandras <markos.chandras@...tec.com>,
	Ralf Baechle <ralf@...ux-mips.org>,
	"Ard Biesheuvel" <ard.biesheuvel@...aro.org>
Subject: [PATCH 0/2] Default platform MAAR implementation

The kernel has previously required platforms making use of MAARs (Memory
Accessibility Attribute Registers) to configure the MAARs in a
platform_maar_init function. This series provides a default/weak
implementation of that function which reuses the data platforms already
provide to the bootmem allocator, and switches Malta to use it. The
result is a reduction in the duplication of data provided by the
platform about the memory map, and a corresponding reduction in the
amount of code needed to support a platform.

Paul Burton (2):
  MIPS: mm: default platform_maar_init using bootmem data
  MIPS: malta: use generic platform_maar_init

 arch/mips/mm/init.c                | 36 ++++++++++++++++++++++++++++++++++--
 arch/mips/mti-malta/malta-memory.c | 25 -------------------------
 2 files changed, 34 insertions(+), 27 deletions(-)

-- 
2.4.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/