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, 28 Sep 2016 18:20:29 -0700 From: Vineet Gupta <vgupta@...opsys.com> To: Andy Lutomirski <luto@...capital.net>, Peter Zijlstra <peterz@...radead.org> Cc: Alexey Brodkin <Alexey.Brodkin@...opsys.com>, arcml <linux-snps-arc@...ts.infradead.org>, Vineet Gupta <Vineet.Gupta1@...opsys.com>, lkml <linux-kernel@...r.kernel.org> Subject: Re: NMI for ARC On 09/28/2016 03:26 PM, Andy Lutomirski wrote: >> Right, so what I think Vineet is asking is if we need to disable NMIs as >> > well, we cannot on x86 disable NMIs so no. >> > > The same argument works here, too: an NMI won't set TIF_NEED_RESCHED > without sending an IPI, so we can't miss a wakeup. But what exact wakeup miss are we taking about here. If intr were NOT disabled, how could this happen. Just trying to understand the need for "irqs-disabled" in resume_{user,kernel}_* The intr disabled before reg file restore makes complete sense though.
Powered by blists - more mailing lists