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: <20090413034058.GB11652@elte.hu>
Date:	Mon, 13 Apr 2009 05:40:58 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Dave Jones <davej@...hat.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
	Mike Galbraith <efault@....de>,
	Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
	Len Brown <len.brown@...el.com>,
	Zhao Yakui <yakui.zhao@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 1/7] use smp_call_function_single() in
	arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c


* Dave Jones <davej@...hat.com> wrote:

> On Mon, Apr 13, 2009 at 09:30:02AM +0930, Rusty Russell wrote:
>  > From: Andrew Morton <akpm@...ux-foundation.org>
>  > 
>  > Impact: fix sysbench(oltp)+mysql 10% regression with 2.6.30-rc1
>  > 
> 
> This, and the other cpufreq related patches in this series look 
> sound to me. Given the other non-cpufreq bits in the series, do 
> you want to just have these go through Andrew and onto Linus?

the other x86 bits look good to me too. It would be best to do this 
via -mm because the regression was introduced from there too so the 
'lets do a revert and these patches in the next cycle' versus 'lets 
do these fixes right now' decision should be driven from there too.

Thanks,

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