linux-kernel - Re: [PATCH 2/2] pm_qos: make update_request callable from interrupt context

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: <alpine.LFD.2.00.1006091146010.2933@localhost.localdomain>
Date:	Wed, 9 Jun 2010 11:46:27 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Florian Mickler <florian@...kler.org>
cc:	pm list <linux-pm@...ts.linux-foundation.org>,
	james.bottomley@...e.de, markgross@...gnar.org,
	mgross@...ux.intel.com, Frederic Weisbecker <fweisbec@...il.com>,
	Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] pm_qos: make update_request callable from interrupt
 context

On Wed, 9 Jun 2010, florian@...kler.org wrote:

> The pm_qos framework has to guarantee atomic notifications so that
> drivers can request and release constraints at all times while no races
> occur.
> 
> In order to avoid implementing a secondary notification chain in which
> listeners might sleep, we demand that every listener implements it's
> notification so that it can run in interrupt context. The listener is in
> a better position to know if races are harmful or not.

That breaks existing notifiers.

Thanks,

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