Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752607AbbHTS3T (ORCPT ); Thu, 20 Aug 2015 14:29:19 -0400 Received: from casper.infradead.org ([85.118.1.10]:60228 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752063AbbHTS3Q (ORCPT ); Thu, 20 Aug 2015 14:29:16 -0400 Date: Thu, 20 Aug 2015 20:29:03 +0200 From: Peter Zijlstra To: Kevin Hao Cc: Michael Ellerman , linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, Ingo Molnar , Benjamin Herrenschmidt Subject: Re: [PATCH 1/8] jump_label: no need to acquire the jump_label_mutex in jump_lable_init() Message-ID: <20150820182903.GA3161@worktop.event.rightround.com> References: <1440072876-8321-1-git-send-email-haokexin@gmail.com> <1440072876-8321-2-git-send-email-haokexin@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1440072876-8321-2-git-send-email-haokexin@gmail.com> User-Agent: Mutt/1.5.22.1 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 583 Lines: 12 On Thu, Aug 20, 2015 at 08:14:29PM +0800, Kevin Hao wrote: > The jump_label_init() run in a very early stage, even before the > sched_init(). So there is no chance for concurrent access of the > jump label table. It also doesn't hurt to have it. Its better to be consistent and conservative with locking unless there is a pressing need. -- 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/