linux-kernel - Re: [PATCH RT] sched: Do not clear PF_NO_SETAFFINITY flag in select_fallback

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]

Message-ID: <20150217093726.GD26177@linutronix.de>
Date:	Tue, 17 Feb 2015 10:37:26 +0100
From:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	linux-rt-users <linux-rt-users@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Clark Williams <williams@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	stable-rt@...r.kernel.org
Subject: Re: [PATCH RT] sched: Do not clear PF_NO_SETAFFINITY flag in
 select_fallback_rq()

* Steven Rostedt | 2014-07-01 11:14:44 [-0400]:

>I talked with Peter Zijlstra about this, and he told me that the clearing
>of the PF_NO_SETAFFINITY flag was to deal with the optimization of
>migrate_disable/enable() that ignores tasks that have that flag set. But
>that optimization was removed when I did a rework of the cpu hotplug code.

This has been already applied. You took it into v3.14 and while applying
the latest v3.14 patches it made its way into v3.18 as well.

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