linux-kernel - [PATCH 00/21] amd64

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 16 Nov 2009 15:16:27 +0100
From:	Borislav Petkov <borislav.petkov@....com>
To:	<linux-kernel@...r.kernel.org>
CC:	<x86@...nel.org>, <norsk5@...oo.com>
Subject: [PATCH 00/21] amd64_edac queue for .33

Hi all,

here is the current patchqueue of amd64_edac fixes/improvements for the
next merge window, among which are a faster syndrome decoding algorithm,
DDR3 support, important fixes and a large amount of cleanups.


01,02,05,06,07,08,09,10,12,13,14,16,21:

cleanups/simplifications/code unification/debug enhancements/speedups

03:

this one is in -tip, listed for the sake of completenes here

04:

final cpumask_t -> struct cpumask conversion bits

11,17,18:

DDR3 support

15:

F10h revD fix

19:

much faster and leaner x4/x8 syndrome decoding

20:

important fix since syndrome to channel decoding should be done only
when in ganged mode.

The patches are also at

git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git for-next

for those who would like to give them a run.

arch/x86/include/asm/msr.h  |    4 +-
 arch/x86/lib/msr.c          |   46 +-
 drivers/edac/amd64_edac.c   | 1251 +++++++++++++++++++------------------------
 drivers/edac/amd64_edac.h   |   62 ++-
 drivers/edac/edac_core.h    |    1 +
 drivers/edac/edac_mc.c      |   24 +
 drivers/edac/edac_mce_amd.c |    2 +-
 7 files changed, 642 insertions(+), 748 deletions(-)


-- 
Regards/Gruss,
Boris.

--
Advanced Micro Devices, Inc.
Operating Systems Research Center

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