Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp714700imm; Wed, 10 Oct 2018 03:10:42 -0700 (PDT) X-Google-Smtp-Source: ACcGV62RUX7SR7uWMzJfpWZ1jGIymk7cav/vUVDxKGaK3jBN8fHrPgAMTJmn7lhMHSkMqJtGWVm+ X-Received: by 2002:a63:450b:: with SMTP id s11-v6mr29849807pga.301.1539166242429; Wed, 10 Oct 2018 03:10:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539166242; cv=none; d=google.com; s=arc-20160816; b=UwqqngFXVZl5xAtjmWw0CTW5m0lxitIgFEmI9eeoHRrlg65yLy2+eKRamlwxNtpEIU /x2MfYyS0pa2cAJGKxfQL19h82YsHOEvh1FmsXxC8QMDiWrFNUvsunYJbPwcB5YQALOX WZk+VPuImVUbkKfQd2dXdP9xT9bxqvWmMr65MPbqVg5CNXX8kcWi/GfFYIobKb2Ba8zJ UyVFHBTjZ3zr6aU9dOBkpGs3IQugRl9qVFPSu/OpP7RBHDT188FOdNMigFff2jbAZUOE 3VsJJEH2wj8Fi3Ehc6cIw1zOFPuo1MrchB8XTuq7FA/Db8km0oSlNeo78rFhj4PZ2HMg qYag== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=xEQ8madIB8bR2DEAjgslyqEK1pQE4mMeQoTcGL52gHI=; b=xgsGObu6k6Vnxc32QsCN2+YIb8qFAC4RP2TyZ+LPkVeRhRsw6JCZl2u+Fo6r9lgX1o 2KmE9l2Sv/47GdbG+m5aLfu+otGOqSr+Jg3PBO3EEZdgv3kJAED2v+7oG2+eL/wW/alj x/ZqpODDRyNnUb8uD5UAWNSXCPuIZX88N3+G8tUZhXNoRsGKS13vfmyDgPjo5lP49VuU BZxrptlwexJzBE+qnud36nOLLEDskPAzm04cxdah833enX85Wo4DiGL56Tva+2D3QjA+ rk/4R6kho6m8jPmvZCPnBorMfhcpEY1w+kuOc+QDqWZY7reGkvk/6aBlbM8knOROid4J 5znw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=wX9pYOIj; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 1-v6si24100480plk.405.2018.10.10.03.10.23; Wed, 10 Oct 2018 03:10:42 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=wX9pYOIj; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726970AbeJJRbZ (ORCPT + 99 others); Wed, 10 Oct 2018 13:31:25 -0400 Received: from mail.kernel.org ([198.145.29.99]:59996 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726862AbeJJRbZ (ORCPT ); Wed, 10 Oct 2018 13:31:25 -0400 Received: from mail-wr1-f52.google.com (mail-wr1-f52.google.com [209.85.221.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B6DFF214FF for ; Wed, 10 Oct 2018 10:09:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1539166198; bh=xEQ8madIB8bR2DEAjgslyqEK1pQE4mMeQoTcGL52gHI=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=wX9pYOIj//ctLMT1HMNTYWmBTSusXxyqKVkhwC71cqXgIKIzawG22357eq8On9kK+ XGmuI5eQ1waBOBSvqTCsv2U3IC+eiheC9PYxyJCck1lIu+lC9p37uag4i08G8ZLpre +B7uugLQ7e211AjrBw2/P2IpmZxzhczlj0D+5+fQ= Received: by mail-wr1-f52.google.com with SMTP id y16so5043139wrw.3 for ; Wed, 10 Oct 2018 03:09:57 -0700 (PDT) X-Gm-Message-State: ABuFfogQWyE3A5bsIztQhC+alkwqjoI0x36uORqcNoqT0mhftQoKIxmK JGDy9pEgNLNBouI85iFg0S5JAgqyi4NqWcQ00O8= X-Received: by 2002:a5d:4306:: with SMTP id h6-v6mr18702524wrq.189.1539166196159; Wed, 10 Oct 2018 03:09:56 -0700 (PDT) MIME-Version: 1.0 References: <20181009153439eucas1p19956dc093074fb7603ad4b39d7cd215a~b_qPT4nMA1415514155eucas1p16@eucas1p1.samsung.com> <20181010095639eucas1p2aa4f4906cac34deb0cfb14383199e3c5~cNsaskok62622626226eucas1p2n@eucas1p2.samsung.com> In-Reply-To: <20181010095639eucas1p2aa4f4906cac34deb0cfb14383199e3c5~cNsaskok62622626226eucas1p2n@eucas1p2.samsung.com> From: Krzysztof Kozlowski Date: Wed, 10 Oct 2018 12:09:44 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] config: arm: exynos: remove PROVE_LOCKING from defconfig To: l.luba@partner.samsung.com Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, =?UTF-8?B?QmFydMWCb21pZWogxbtvxYJuaWVya2lld2ljeg==?= , kgene@kernel.org, Marek Szyprowski Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 10 Oct 2018 at 11:56, Lukasz Luba wrote: > > Hi Krzysztof, > > Is it still valid that the Exynos has locking issues? The prepare lock of clocks was not solved entirely. We just implemented a set of workarounds. > Or is it enabled 'just-in-case'? Yes, all debugging features are implemented just in case to spot any issue as early as possible. > On arm64 the config misses that setting. > Should be enabled there as well? Because it is a shared defconfig among all platforms and apparently no one wanted to convincing others to enable it. > You have introduced this entry a year ago, probably during bug > investigation. Actually not, I enabled it much later after issues where discovered. > The issue is in lockdep, the setting which enables it in Exynos > is prove_locking. For now, just get rid of the second. > My tests showed lockdep impact and not other minor debug features > enabled. You did not reply directly to my comment - you disabled all debug for locking. It seems you are unaware of this so I question your test results. If you run tests on this patch, then basically you compared existing config with a config stripped out of debugging around locks. I understand that this is not what you wanted... Best regards, Krzysztof