From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757065Ab3CFKeN (ORCPT ); Wed, 6 Mar 2013 05:34:13 -0500 Received: from mail-ee0-f49.google.com ([74.125.83.49]:53301 "EHLO mail-ee0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754166Ab3CFKeK (ORCPT ); Wed, 6 Mar 2013 05:34:10 -0500 Date: Wed, 6 Mar 2013 11:34:06 +0100 From: Ingo Molnar To: Ming Lei Cc: Peter Zijlstra , Ingo Molnar , Linux Kernel Mailing List Subject: Re: lockdep: access percpu variable too early Message-ID: <20130306103406.GB16827@gmail.com> References: <20130306102057.GB6587@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 * Ming Lei wrote: > On Wed, Mar 6, 2013 at 6:20 PM, Ingo Molnar wrote: > > > > What's the practical effect of it? Do we copy the value from the boot CPU and > > thus the secondary CPUs start with slightly increased stats? > > Yes, it is the major effect. > > Also the arch dependent __my_cpu_offset might be initialized a bit late. I suspect we could try to fix it - post-initializing it after percpu setup sounds like a viable option, if it does not get too ugly. Thanks, Ingo