Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932561Ab3DBO7O (ORCPT ); Tue, 2 Apr 2013 10:59:14 -0400 Received: from mail-ob0-f179.google.com ([209.85.214.179]:63359 "EHLO mail-ob0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932465Ab3DBO7N (ORCPT ); Tue, 2 Apr 2013 10:59:13 -0400 MIME-Version: 1.0 In-Reply-To: <20130402145536.GA31757@gulag1.americas.sgi.com> References: <5159C147.70800@sgi.com> <1364847069-2887-1-git-send-email-nzimmer@sgi.com> <1364847069-2887-2-git-send-email-nzimmer@sgi.com> <20130402145536.GA31757@gulag1.americas.sgi.com> Date: Tue, 2 Apr 2013 20:29:12 +0530 Message-ID: Subject: Re: [PATCH v6 1/2] cpufreq: split the cpufreq_driver_lock and use the rcu From: Viresh Kumar To: Nathan Zimmer Cc: rjw@sisk.pl, cpufreq@vger.kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 550 Lines: 11 On 2 April 2013 20:25, Nathan Zimmer wrote: > The lock is unneeded if we expect register and unregister driver to not be > called from muliple threads at once. I didn't make that assumption. Hmm.. But doesn't rcu part take care of that too?? Two writers updating stuff simultaneously? -- 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/