Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932699Ab3CLLZb (ORCPT ); Tue, 12 Mar 2013 07:25:31 -0400 Received: from mail-ve0-f176.google.com ([209.85.128.176]:50613 "EHLO mail-ve0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932228Ab3CLLZ3 (ORCPT ); Tue, 12 Mar 2013 07:25:29 -0400 MIME-Version: 1.0 In-Reply-To: <20130312105638.GQ4977@n2100.arm.linux.org.uk> References: <1362663356-21151-1-git-send-email-tom.leiming@gmail.com> <20130312105638.GQ4977@n2100.arm.linux.org.uk> Date: Tue, 12 Mar 2013 19:25:28 +0800 Message-ID: Subject: Re: [PATCH v1] ARM: keep __my_cpu_offset consistent with generic one From: Ming Lei To: Russell King - ARM Linux Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Peter Zijlstra , Ingo Molnar , Rob Herring , Will Deacon , Nicolas Pitre 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: 1562 Lines: 39 On Tue, Mar 12, 2013 at 6:56 PM, Russell King - ARM Linux wrote: >> >> Looks no one objects the patch, so I has submitted it into Russell's >> patch system, and hope it can be pushed to linus tree soon and >> make LOCK_STAT/DEBUG_LOCKDEP usable on ARMv7. > > I'm not convinced it is correct. Is the percpu data as stored in the > kernel image (in other words, at offset zero) supposed to be read only? It should have been used after setup_per_cpu_areas(). > If so, the above means that we'll be accessing that rather than the > copy of the percpu data we should be accessing. I admit the patch is a work around for the problem, but it is harmless to make lockdep workable on arm at least. > The percpu data areas are allocated by setup_per_cpu_areas() - that's > where we should be initializing this, just like it's done on PowerPC. >From the entry of start_kernel to setup_per_cpu_areas, there are many locks which will be acquired/released, so the percpu variable in lock_release has to be used early now. Either disabling lockdep during the period or introducing stupid/simple percpu variable inside lockdep may fix the probem, but looks both aren't perfect. So the workaround is proposed in this patch... Ingo and Peter, what is your opinion on the problem? Thanks -- Ming Lei -- 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/