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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071214200605.GA17424@one.firstfloor.org>
Date:	Fri, 14 Dec 2007 21:06:05 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Eduard-Gabriel Munteanu <eduard.munteanu@...ux360.ro>,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH] Option to disable AMD C1E (allows dynticks to work)

> Well, that would interfere with the acpi-idle code.

How so? idle notifiers should work for acpi idle too.

> Anyway the idle notifiers is a pretty artificial interface which is on
> my get rid of it list anyway.

The original use cases were: 
- Accounting for idle time with stopped counters in oprofile and eliminate
the need for idle=poll.
That never was implemented unfortunately but would be still a worthy
feature I think.
- Perfmon for similar uses.
- noidletick -- my original noidletick implementation used the idle
notifiers similar to the s390 implementation. Obsolete now. 

Right now it is used for the machine check early notification, but I never
liked that (imho it just "fixes" a non problem only relevant 
in non realistic testing situations) and it would be fine to drop that one 
I think.  In fact I already made it a config in the patchkit to use the 64bit
mce code on 32bit too.

-Andi

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ