| 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
| ||
|
Date: Mon, 12 Aug 2013 17:54:21 +0000 From: "Luck, Tony" <tony.luck@...el.com> To: Mauro Carvalho Chehab <m.chehab@...sung.com>, Borislav Petkov <bp@...en8.de> CC: "Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>, "bhelgaas@...gle.com" <bhelgaas@...gle.com>, "rostedt@...dmis.org" <rostedt@...dmis.org>, "rjw@...k.pl" <rjw@...k.pl>, "lance.ortiz@...com" <lance.ortiz@...com>, "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>, "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: RE: [PATCH 3/3] mce: acpi/apei: trace: Enable ghes memory error trace event >> We are, of course, going to have only one tracepoint which reports >> memory errors, not two. > > Yes, that's my point. Is life that simple? We have systems that have no EDAC driver (in some cases because the architecture precludes one from ever being written, in other because we either don't have the documentation, or because no driver has been written yet). Systems also have varying degrees of APEI support (from none at all, to full support ... possibly we may have some with apparent support, but BIOS provides bogus information ... assuming BIOS folks live up/down to our usual expectations). -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/
Powered by blists - more mailing lists