linux-kernel - RE: [PATCH 1/3] mce: Add a msg string to the MCE tracepoint

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 29 Feb 2012 17:20:35 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Mauro Carvalho Chehab <mchehab@...hat.com>,
	Borislav Petkov <bp@...64.org>
CC:	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
	Ingo Molnar <mingo@...e.hu>,
	EDAC devel <linux-edac@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/3] mce: Add a msg string to the MCE tracepoint

> IMHO, before removing those fields, it would be better to first implement
> what is there at the mcelog userspace parser for the Intel machines into
> kernelspace (or to look into its source code), and check what registers
> aren't used by either AMD 64 MCE decoder or by the Intel MCE decoder.
>
> Tony,
>
> Is there anyone at Intel working on porting it to kernelspace?

The mcelog code just looks at model specific fields in MCi_STATUS
and MCi_MISC.  We could move it to the kernel - but I don't see
much value in doing so.  In this case all the information we need
is carried in status/misc - so as long as we keep all of those
bits (and the cpu family/model) we can safely decode/analyze later.

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