Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753804AbaBJRfU (ORCPT ); Mon, 10 Feb 2014 12:35:20 -0500 Received: from e28smtp01.in.ibm.com ([122.248.162.1]:34550 "EHLO e28smtp01.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753022AbaBJRfQ (ORCPT ); Mon, 10 Feb 2014 12:35:16 -0500 Message-ID: <52F90C8C.9050203@linux.vnet.ibm.com> Date: Mon, 10 Feb 2014 22:59:48 +0530 From: "Srivatsa S. Bhat" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120828 Thunderbird/15.0 MIME-Version: 1.0 To: Oleg Nesterov CC: paulus@samba.org, rusty@rustcorp.com.au, peterz@infradead.org, tglx@linutronix.de, akpm@linux-foundation.org, mingo@kernel.org, paulmck@linux.vnet.ibm.com, tj@kernel.org, walken@google.com, ego@linux.vnet.ibm.com, linux@arm.linux.org.uk, linux-kernel@vger.kernel.org, Tony Luck , Borislav Petkov , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, linux-edac@vger.kernel.org Subject: Re: [PATCH 19/51] x86, therm_throt.c: Fix CPU hotplug callback registration References: <20140205220251.19080.92336.stgit@srivatsabhat.in.ibm.com> <20140205220759.19080.36356.stgit@srivatsabhat.in.ibm.com> <20140210155323.GA8911@redhat.com> In-Reply-To: <20140210155323.GA8911@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 14021017-4790-0000-0000-00000CA7726E Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/10/2014 09:23 PM, Oleg Nesterov wrote: > On 02/06, Srivatsa S. Bhat wrote: >> >> --- a/arch/x86/kernel/cpu/mcheck/therm_throt.c >> +++ b/arch/x86/kernel/cpu/mcheck/therm_throt.c >> @@ -319,7 +319,7 @@ static __init int thermal_throttle_init_device(void) >> if (!atomic_read(&therm_throt_en)) >> return 0; >> >> - register_hotcpu_notifier(&thermal_throttle_cpu_notifier); >> + cpu_maps_update_begin(); >> >> #ifdef CONFIG_HOTPLUG_CPU >> mutex_lock(&therm_cpu_lock); >> @@ -333,6 +333,9 @@ static __init int thermal_throttle_init_device(void) >> mutex_unlock(&therm_cpu_lock); >> #endif >> >> + __register_hotcpu_notifier(&thermal_throttle_cpu_notifier); >> + cpu_maps_update_done(); > > > Off-topic, but it seems that after this change therm_cpu_lock can die. > Of course this needs another patch (if I am right). > I'm not sure I understood that clearly. Can you please explain? I'm guessing that you are referring to some problem with the #ifdef CONFIG_HOTPLUG_CPU around mutex_lock/unlock(&therm_cpu_lock) ? Regards, Srivatsa S. Bhat -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/