From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D7D39C2BA19 for ; Mon, 13 Apr 2020 16:56:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 8CBA92076D for ; Mon, 13 Apr 2020 16:56:44 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="cpz7mxba" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732214AbgDMQ4n (ORCPT ); Mon, 13 Apr 2020 12:56:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47894 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1731673AbgDMQ4l (ORCPT ); Mon, 13 Apr 2020 12:56:41 -0400 Received: from mail-pj1-x1042.google.com (mail-pj1-x1042.google.com [IPv6:2607:f8b0:4864:20::1042]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5E075C0A3BE2 for ; Mon, 13 Apr 2020 09:56:41 -0700 (PDT) Received: by mail-pj1-x1042.google.com with SMTP id nu11so4024414pjb.1 for ; Mon, 13 Apr 2020 09:56:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=cYxFIXZ3Oep1Nvg46stgQrEWlEoqYyS7FyRUU0yEbnU=; b=cpz7mxbaVIihtI5Z2YQX63QZSHlMrnt6mjLjQt4nECoY7LWSqS3j3C6FJLqaWAUTt8 r1EasPcYfH5L8KnX3osbiglmPu0cAXo/keN6VU3SFKFiOM+lUrae6/gVrANEfhsxhUl1 vEIPuDPIYQRZUynqGirnxTVSCbnm6ubZ8tSlc/GYJWQTiiEUYbDBg6PSnGOMJHgSGse+ 88WJuipwslDyXizj/qa6+Glxm1ZTPsKc2GA5xSPtpM+GuliOYNQ0cZPVZ9OYqX2XRfTP kLo6Ngr6CUfCa8Dfq7PRetr0K/16m06xVAVMcGQFdBwM3EL5dm1j3VLXF/C6lhebhOtC cllA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=cYxFIXZ3Oep1Nvg46stgQrEWlEoqYyS7FyRUU0yEbnU=; b=UvQWMu6GFhiOnjlOMTk5lb1jRuxaPMXF9BMi01gMQ7pDjiaJue4sw+hD8U7xru3gkx HbvozPE3GLjwBHM1bzioBhO8qMVl/kmZskhm3RfoYLrzdAHy6y6S/298Lj500SBYl3Ih px5KHrH6srCblxXb0PdIFKsxaTO+XBFIG/n7i0nTPHaP2cB3googY3T8Ouv/oP0pWJBy NTwXfzgcGL5sb0QHV8ww56lVy8P9HbsDuGKA8eNGrdf2cU66XHtmQa4fvoazcYn3QJIE gPcYIoYzgkuNyT3bKYGnw1xOhBqLiD6EnJIJchECCV4rqEZTYAOSTue4uF049MkkeAQa kRCA== X-Gm-Message-State: AGi0PuaHJdKr0EkJYt2h7zjja7CzEz5xoQASD/K5sXPjnAZ/Ku+YZGyF h3ghoGQ1kphdEdQMs5YFRGd1Uw== X-Google-Smtp-Source: APiQypKvDNVn1PLsRgvoEtqETwrmavvjWo5FoLCjth7E4O2lzzM+yCFNAxkNp0Dov2d38drJoFC5zQ== X-Received: by 2002:a17:902:cf87:: with SMTP id l7mr6464052ply.307.1586797000706; Mon, 13 Apr 2020 09:56:40 -0700 (PDT) Received: from xps15 (S0106002369de4dac.cg.shawcable.net. [68.147.8.254]) by smtp.gmail.com with ESMTPSA id o125sm8225592pgo.74.2020.04.13.09.56.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 13 Apr 2020 09:56:39 -0700 (PDT) Date: Mon, 13 Apr 2020 10:56:38 -0600 From: Mathieu Poirier To: Suzuki K Poulose Cc: saiprakash.ranjan@codeaurora.org, mike.leach@linaro.org, swboyd@chromium.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org Subject: Re: [PATCH] coresight: tmc: Read TMC mode only when TMC hw is enabled Message-ID: <20200413165638.GA28804@xps15> References: <20200409113538.5008-1-saiprakash.ranjan@codeaurora.org> <9a792e3e-5a17-156d-4b59-4a3ec8f9993e@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9a792e3e-5a17-156d-4b59-4a3ec8f9993e@arm.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 13, 2020 at 12:17:21AM +0100, Suzuki K Poulose wrote: > Hi Sai, > > On 04/09/2020 12:35 PM, Sai Prakash Ranjan wrote: > > Reading TMC mode register in tmc_read_prepare_etb without > > enabling the TMC hardware leads to async exceptions like > > the one in the call trace below. This can happen if the > > user tries to read the TMC etf data via device node without > > setting up source and the sink first which enables the TMC > > hardware in the path. So make sure that the TMC is enabled > > before we try to read TMC data. > > So, one can trigger the same SError by simply : > > $ cat /sys/bus/coresight/device/tmc_etb0/mgmt/mode A true TMC-ETB is a rarity nowadays... What boards was this tested on? I don't know if it is how the IP behaves or how things are connected on Sai's specific board but doing echo'ing tmc_etf0/mgmt/mode on my Juno R0 doesn't give rise to any problems. That certainly doesn't mean it can't happen on another platform. > > > And also : > > > > > Kernel panic - not syncing: Asynchronous SError Interrupt > > CPU: 7 PID: 2605 Comm: hexdump Tainted: G S 5.4.30 #122 > > Call trace: > > dump_backtrace+0x0/0x188 > > show_stack+0x20/0x2c > > dump_stack+0xdc/0x144 > > panic+0x168/0x36c > > panic+0x0/0x36c > > arm64_serror_panic+0x78/0x84 > > do_serror+0x130/0x138 > > el1_error+0x84/0xf8 > > tmc_read_prepare_etb+0x88/0xb8 > > tmc_open+0x40/0xd8 > > misc_open+0x120/0x158 > > chrdev_open+0xb8/0x1a4 > > do_dentry_open+0x268/0x3a0 > > vfs_open+0x34/0x40 > > path_openat+0x39c/0xdf4 > > do_filp_open+0x90/0x10c > > do_sys_open+0x150/0x3e8 > > __arm64_compat_sys_openat+0x28/0x34 > > el0_svc_common+0xa8/0x160 > > el0_svc_compat_handler+0x2c/0x38 > > el0_svc_compat+0x8/0x10 > > > > Fixes: 4525412a5046 ("coresight: tmc: making prepare/unprepare functions generic") > > Reported-by: Stephen Boyd > > Signed-off-by: Sai Prakash Ranjan > > --- > > drivers/hwtracing/coresight/coresight-tmc.c | 5 +++++ > > drivers/hwtracing/coresight/coresight-tmc.h | 1 + > > 2 files changed, 6 insertions(+) > > > > diff --git a/drivers/hwtracing/coresight/coresight-tmc.c b/drivers/hwtracing/coresight/coresight-tmc.c > > index 1cf82fa58289..7bae69748ab7 100644 > > --- a/drivers/hwtracing/coresight/coresight-tmc.c > > +++ b/drivers/hwtracing/coresight/coresight-tmc.c > > @@ -62,11 +62,13 @@ void tmc_flush_and_stop(struct tmc_drvdata *drvdata) > > void tmc_enable_hw(struct tmc_drvdata *drvdata) > > { > > + drvdata->enable = true; > > writel_relaxed(TMC_CTL_CAPT_EN, drvdata->base + TMC_CTL); > > } > > void tmc_disable_hw(struct tmc_drvdata *drvdata) > > { > > + drvdata->enable = false; > > writel_relaxed(0x0, drvdata->base + TMC_CTL); > > } > > @@ -102,6 +104,9 @@ static int tmc_read_prepare(struct tmc_drvdata *drvdata) > > { > > int ret = 0; > > + if (!drvdata->enable) > > + return -EINVAL; > > + Proceeding this way would mean that ETB and ETF internal memory buffers can't be read unless the device is enabled and collecting trace. That is not practical because 1) it changes the way the sysfs interface works on all boards where there isn't a problem and 2) it makes it very difficult to capture the correct data. When the device is __not__ enabled, does reading any of the registers under "/sys/bus/coresight/devices/tmc_etbX/mgmt/" also cause a problem or is it just 'mode'? Thanks, Mathieu > > Does this check always guarantee that the TMC is enabled when > we actually get to reading the MODE ? This needs to be done > under the spinlock. > > Cheers > Suzuki > > >