linux-kernel - Re: [Patch 0/7] Per cpu thread hotplug infrastructure

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: <20120718235402.GP2435@linux.vnet.ibm.com>
Date:	Wed, 18 Jul 2012 16:54:02 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <peterz@...radead.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Namhyung Kim <namhyung@...nel.org>
Subject: Re: [Patch 0/7] Per cpu thread hotplug infrastructure - V3

On Wed, Jul 18, 2012 at 11:06:52PM +0530, Srivatsa S. Bhat wrote:
> On 07/16/2012 08:52 PM, Paul E. McKenney wrote:
> > On Mon, Jul 16, 2012 at 10:42:34AM -0000, Thomas Gleixner wrote:
> >> The following series implements the infrastructure for parking and
> >> unparking kernel threads to avoid the full teardown and fork on cpu
> >> hotplug operations along with management infrastructure for hotplug
> >> and users.
> >>
> >> Changes vs. V2:
> >>
> >>  Use callbacks for all functionality. Thanks to Rusty for pointing
> >>  that out. It makes the use sites nice and simple and keeps all the
> >>  code which would be duplicated otherwise on the core.
> > 
> > Hello, Thomas,
> > 
> > What version should I apply this patchset to?  I tried v3.5-rc7, but
> > got lots of warnings (one shown below) and the watchdog patch did not
> > apply.
> > 
> 
> Hi Paul,
> 
> This patchset applies cleanly on Thomas' smp/hotplug branch in the -tip
> tree.

Thank you, Srivatsa, works much better.  Still get "scheduling while
atomic", looking into that.

I suppose I should have been able to guess where it was based...
Ah, well...

							Thanx, Paul

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