linux-kernel - RE: [PATCH 4/6] x86/cpufreq: use cpumask

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]

Date:	Mon, 21 Sep 2009 11:44:59 -0500
From:	"Langsdorf, Mark" <mark.langsdorf@....com>
To:	"'Rusty Russell'" <rusty@...tcorp.com.au>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Yinghai Lu <yinghai@...nel.org>, Avi Kivity <avi@...hat.com>,
	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...hat.com>,
	"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>
Subject: RE: [PATCH 4/6] x86/cpufreq: use cpumask_copy instead of =

> On Thu, 11 Jun 2009 05:12:16 am Langsdorf, Mark wrote:
> > > powernow_k8_target is problematic: it grabs a mutex.  cpufreq
> > > people, is this called often?
> >
> > Yes.  It's the function that makes a frequency change
> > happen, so 5+ times per second per core isn't
> > unreasonable.
> 
> Right, so we need to revisit this.  I'll leave it for the 
> moment and put it on my TODO list.

Rusty -

Did you ever get any ideas on a solution to this?  I'm
getting reports that the set_cpus_allowed_ptr() in
powernow_k8_target() is breaking with changeset
ebc79c4f8da0f92efa968e0328f32334a2ce80cf .  I haven't
changed the powernow_k8 code, so I suspect something
happened to set_cpus_allowed_ptr().

-Mark Langsdorf
Operating System Research Center
AMD
--
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/