From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756471AbbBQJhf (ORCPT ); Tue, 17 Feb 2015 04:37:35 -0500 Received: from www.linutronix.de ([62.245.132.108]:42893 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756445AbbBQJhc (ORCPT ); Tue, 17 Feb 2015 04:37:32 -0500 Date: Tue, 17 Feb 2015 10:37:26 +0100 From: Sebastian Andrzej Siewior To: Steven Rostedt Cc: LKML , linux-rt-users , Thomas Gleixner , Clark Williams , Peter Zijlstra , stable-rt@vger.kernel.org Subject: Re: [PATCH RT] sched: Do not clear PF_NO_SETAFFINITY flag in select_fallback_rq() Message-ID: <20150217093726.GD26177@linutronix.de> References: <20140701111444.0cfebaa1@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20140701111444.0cfebaa1@gandalf.local.home> X-Key-Id: 97C4700B X-Key-Fingerprint: 09E2 D1F3 9A3A FF13 C3D3 961C 0688 1C1E 97C4 700B User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * 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