linux-kernel - Re: NMI watchdog setup_lapic_nmi

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <7c86c4470810071657l691a2319uc3edbe8ec7c473b7@mail.gmail.com>
Date:	Wed, 8 Oct 2008 01:57:45 +0200
From:	"stephane eranian" <eranian@...glemail.com>
To:	"Andi Kleen" <andi@...stfloor.org>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, mingo@...e.hu, tglx@...utronix.de,
	"Shaohua Li" <shaohua.li@...el.com>
Subject: Re: NMI watchdog setup_lapic_nmi_watchdog() problem

Andi,

On Wed, Oct 8, 2008 at 1:45 AM, Andi Kleen <andi@...stfloor.org> wrote:
>> If you remove the 'cheap hack', disabling/enabling works. That's why
>> I'd like to better
>> understand was is going on with suspend/resume.
>
> The hack was done because there wasn't an available CPU global enable flag
> for the nmi watchdog. So resume would possible reenable it unnecessarily
> If there was one it could just check that.
>
I am not sure what you mean by 'CPU global enable flag'.

Are you talking about a per-cpu variable or a truly global variable?

Isn't that what nmi_active is today?

As for per-cpu, there is wd_enabled.
--
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/