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: Wed, 06 Jun 2012 09:36:52 +0800 From: Chen Gong <gong.chen@...ux.intel.com> To: Borislav Petkov <bp@...64.org> CC: Thomas Gleixner <tglx@...utronix.de>, LKML <linux-kernel@...r.kernel.org>, tony.luck@...el.com, x86@...nel.org, Peter Zijlstra <peterz@...radead.org> Subject: Re: [patch 2/2] x86: mce: Implement cmci poll mode for intel machines δΊ 2012/6/5 20:57, Borislav Petkov ει: > On Tue, Jun 05, 2012 at 07:47:20PM +0800, Chen Gong wrote: >>> static void intel_threshold_interrupt(void) >>> { >>> + if (cmci_storm_detect()) >>> + return; >>> machine_check_poll(MCP_TIMESTAMP, &__get_cpu_var(mce_banks_owned)); >>> mce_notify_irq(); >>> } >> I think cmci_storm_detect should be placed in the machine_check_poll, >> not out of it. Because machine_check_poll it the core execution logic >> for CMCI handling, in the meanwhile, poll timer and mce-inject module >> call machine_check_poll at any time. > Are you saying you need CMCI throttling for when you inject MCEs? Yes, I am just afraid similar situation happening when injecting MCEs or poll timer running too fast, which is like a pseduo CMCI storm. Maybe similar logic behind CMCI_STORM can be used there. -- 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