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

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

Date:	Thu, 1 Mar 2012 18:28:47 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Borislav Petkov <bp@...64.org>,
	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>
CC:	Mauro Carvalho Chehab <mchehab@...hat.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

> > My concern is; on Sandy Bridge, is it safe to gather info about the DIMM
> > location in/from machine check context in a reasonable time span?
>
> Well, what amd64_edac does is "buffer" the required lookup info so
> whenever you get an error, you simply lookup the channel and chip select
> - all ops which can be done in atomic context.

Yes - we could pre-read all the config space registers ahead of time and
save them in memory (none of the values should change - except if the platform
supports hot-plug for memory). Total is only a few Kbytes. Then decode in
machine check context is both safe, and fast.

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