linux-kernel - Re: latest -git: WARNING: at arch/x86/kernel/ipi.c:123 send_IPI_mask

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: <20080825204700.GB27030@redhat.com>
Date:	Mon, 25 Aug 2008 16:47:02 -0400
From:	Dave Jones <davej@...hat.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Vegard Nossum <vegard.nossum@...il.com>,
	"H. Peter Anvin" <hpa@...nel.org>,
	the arch/x86 maintainers <x86@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: latest -git: WARNING: at arch/x86/kernel/ipi.c:123
	send_IPI_mask_bitmask+0xc3/0xe0()

On Mon, Aug 25, 2008 at 10:36:49PM +0200, Andi Kleen wrote:
 
 > > If we get a thermal event that was caused by temporary
 > > increased workload, temperature will drop off again when that workload
 > > is complete.
 > 
 > But none of the cpufreq governours do this. They only care about
 > load, not about temperature.

Which is good enough to stop p4 laptops from shutting down as
soon as they've finished booting up.

 > > For sustained workloads we'd get additional thermal events, at which
 > > time we make a decision "ok, we've throttled as far as we can, and
 > > things are still going badly, power off".
 > 
 > That is what the ACPI driver does when the trip point is reached.

yes, except for that "we've throttled" part.
 
	Dave

-- 
http://www.codemonkey.org.uk
--
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/