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
| ||
|
Message-ID: <ef3e4bd4f8254b42a6d73356b4eec7f8@intel.com> Date: Wed, 23 Feb 2022 23:03:21 +0000 From: "Luck, Tony" <tony.luck@...el.com> To: "Koralahalli Channabasappa, Smita" <skoralah@....com>, Borislav Petkov <bp@...en8.de>, Smita Koralahalli <Smita.KoralahalliChannabasappa@....com> CC: "x86@...nel.org" <x86@...nel.org>, "linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "H . Peter Anvin" <hpa@...or.com>, "Dave Hansen" <dave.hansen@...ux.intel.com>, Yazen Ghannam <yazen.ghannam@....com> Subject: RE: [RFC PATCH 1/2] x86/mce: Handle AMD threshold interrupt storms > It looks to me most of the code can be shared except in few places > where AMD and Intel use different registers to set error thresholds. Hopefully easy to abstract. > And the fact that AMD's threshold interrupts just handles corrected > errors unlike CMCI. That makes your life much simpler than mine :-) > I'm thinking of coming up with a shared code between both by keeping > the Intel's new storm handling code as base and incorporating AMD > changes on them and send for review. > > Let me know if thats okay? My new Intel code hasn't had Boris look through it yet to point out all the bits where I have bugs, or just make things more complex than they need to be. So it would be helpful if Boris could do at least a quick scan to say my code is a worthy base. I'd hate to see you waste time building a merged version and then have Boris say "Nack". -Tony
Powered by blists - more mailing lists