linux-kernel - Re: [PATCH] smpboot: allow excluding cpus from the smpboot threads

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: <552D34BC.4060109@ezchip.com>
Date:	Tue, 14 Apr 2015 11:39:40 -0400
From:	Chris Metcalf <cmetcalf@...hip.com>
To:	Frederic Weisbecker <fweisbec@...il.com>
CC:	Thomas Gleixner <tglx@...utronix.de>,
	Don Zickus <dzickus@...hat.com>,
	<linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH] smpboot: allow excluding cpus from the smpboot threads

On 04/14/2015 11:23 AM, Frederic Weisbecker wrote:
> On Mon, Apr 13, 2015 at 12:06:50PM -0400, Chris Metcalf wrote:
>> Also, I want to ask Linus to pull the tile-specific changes for nohz_full
>> for the tile architecture.  This includes a copy of the change to add the
>> tick_nohz_full_add_cpus_to() and tick_nohz_full_remove_cpus_from()
>> routines here:
> Hmm, this is going to be too late to push the tick_nohz_full_add_cpus_to()
> stuff for this merge window. This needs to go through nohz core tree and
> we are already in the middle of the merge window.

I'll defer the change in the tilegx network driver until the next merge.
(I guess what I would do is cherrypick the nohz change into the tile tree
to keep it easy to build and just assume it's easy to resolve when it's
pulled for 4.2.)

-- 
Chris Metcalf, EZChip Semiconductor
http://www.ezchip.com

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