From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965292AbcBQMrf (ORCPT ); Wed, 17 Feb 2016 07:47:35 -0500 Received: from mga03.intel.com ([134.134.136.65]:60476 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965076AbcBQMre (ORCPT ); Wed, 17 Feb 2016 07:47:34 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,460,1449561600"; d="scan'208";a="904474137" Message-ID: <1455713251.5622.9.camel@linux.intel.com> Subject: Re: [PATCH] [RFC] kernel/cpu: Use lockref for online CPU reference counting From: Joonas Lahtinen To: Peter Zijlstra , Oleg Nesterov Cc: Intel graphics driver community testing & development , Linux kernel development , Ingo Molnar , David Hildenbrand , "Paul E. McKenney" , "Gautham R. Shenoy" , Chris Wilson , Daniel Vetter Date: Wed, 17 Feb 2016 14:47:31 +0200 In-Reply-To: <20160216110732.GU6357@twins.programming.kicks-ass.net> References: <1455539803-13913-1-git-send-email-joonas.lahtinen@linux.intel.com> <20160215141755.GG6357@twins.programming.kicks-ass.net> <20160215170618.GL6375@twins.programming.kicks-ass.net> <1455612576.4977.11.camel@linux.intel.com> <20160216091440.GT6357@twins.programming.kicks-ass.net> <1455619863.4977.29.camel@linux.intel.com> <20160216110732.GU6357@twins.programming.kicks-ass.net> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.4 (3.18.4-1.fc23) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On ti, 2016-02-16 at 12:07 +0100, Peter Zijlstra wrote: > On Tue, Feb 16, 2016 at 12:51:03PM +0200, Joonas Lahtinen wrote: > > Quoting my original patch; > > > > "See the Bugzilla link for more details. > > If its not in the Changelog it doesn't exist. Patches should be self > contained and not refer to external sources for critical information. The exact locking case in CPUfreq drivers causing a splat is described in the patch. Details were already included, that's why term "more details" was used. This is not exactly taking us closer to a fix, so I'd rather like to discuss about the possibility of adding one more member to task_struct. I added Oleg as CC to catch his attention to re-evaluate based on the previous discussion in this thread. Regards, Joonas -- Joonas Lahtinen Open Source Technology Center Intel Corporation