Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp7395557rwi; Mon, 24 Oct 2022 14:06:27 -0700 (PDT) X-Google-Smtp-Source: AMsMyM5ZFLBn+zk1URRPOxOy5sh/aBr/w9jr9or10Lm2CFmXCr4SGVr33Up8agLDJiKZ0Mk5dHOn X-Received: by 2002:aa7:cad5:0:b0:454:88dc:2c22 with SMTP id l21-20020aa7cad5000000b0045488dc2c22mr32687337edt.352.1666645587216; Mon, 24 Oct 2022 14:06:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666645587; cv=none; d=google.com; s=arc-20160816; b=D1G43ZY6FT0CKxCWv0eg09GqIOvlWHL3wSLmWVmptIGmVV1gWOCMtzVrD2anYIUBE2 mvGev7LKLrPchgheco37gL5aR11D0nGMpKC9zTCuOk0moZE7HXbZqFXZ6KlKN8NbGqJN YRp83fEv1cz7Apv39QgkQObwRy6n5VT/N65W0U08OPmCJnLVnJrO2W6zlb4RzixXnSTe mC8gX9uh8sBHsfEyW8iHYQla2+yBZChi8DjlzJxNPpS1KeNniXFMdhRbXKJf1849rGbn Aj39sOgQ/WK+Dh7YJTUi49AGqRYuya3oQGiZ2jrRkkShsVlz9+KloloIFNAUHt8HcYp3 Mnqw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=DGpN/F1ROAL1TZo48eenhH8UDlbBLbPrPcm4HeVeHhI=; b=gwXsB0f/TEOq3P8US4g/eNR4ewMmKjdixCiVJ3Pb2HZNPVVOVF2TWREna2v3kLpQIN 9TckUMdKjPFpqQ+qaHAqOWAuDxTw2aGgrPP6IFa8uqKhaBHv4BWnvUgimr9MJ2pkMoyc a3cYovcJ+t/kBeaBcmMWsgboXFds7MkeNTxwf4E6W1jLjfd+VJXO9gwD2dxHP2tUwfPi Nm1wow/Hharj2Wx6DP2ysh7vbTYHu/QJ13nXpqwbiM/fguiUyF0kRhdd5zfhNpxCEDbe hm3MLCmI+q8bkXInxcmXaU2AsrPAkQfuXEK6DpWlDBRMvQUhM5DuIn6qxcUzqbWXQj9S ooAg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id g4-20020aa7d1c4000000b0045bccc84cebsi660635edp.71.2022.10.24.14.06.00; Mon, 24 Oct 2022 14:06:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233088AbiJXUGF (ORCPT + 99 others); Mon, 24 Oct 2022 16:06:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49988 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232828AbiJXUFX (ORCPT ); Mon, 24 Oct 2022 16:05:23 -0400 Received: from sin.source.kernel.org (sin.source.kernel.org [IPv6:2604:1380:40e1:4800::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 856B121E101; Mon, 24 Oct 2022 11:26:02 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sin.source.kernel.org (Postfix) with ESMTPS id 4F0F2CE16BB; Mon, 24 Oct 2022 16:09:22 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id AB5DCC433C1; Mon, 24 Oct 2022 16:09:19 +0000 (UTC) Date: Mon, 24 Oct 2022 12:09:29 -0400 From: Steven Rostedt To: Sai Prakash Ranjan Cc: Arnd Bergmann , Masami Hiramatsu , , , , , Subject: Re: [PATCH] asm-generic/io: Add _RET_IP_ to MMIO trace for more accurate debug info Message-ID: <20221024120929.41241e07@gandalf.local.home> In-Reply-To: <20221017143450.9161-1-quic_saipraka@quicinc.com> References: <20221017143450.9161-1-quic_saipraka@quicinc.com> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.7 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 17 Oct 2022 20:04:50 +0530 Sai Prakash Ranjan wrote: > Due to compiler optimizations like inlining, there are cases where > MMIO traces using _THIS_IP_ for caller information might not be > sufficient to provide accurate debug traces. > > 1) With optimizations (Seen with GCC): > > In this case, _THIS_IP_ works fine and prints the caller information > since it will be inlined into the caller and we get the debug traces > on who made the MMIO access, for ex: > > rwmmio_read: qcom_smmu_tlb_sync+0xe0/0x1b0 width=32 addr=0xffff8000087447f4 > rwmmio_post_read: qcom_smmu_tlb_sync+0xe0/0x1b0 width=32 val=0x0 addr=0xffff8000087447f4 > > 2) Without optimizations (Seen with Clang): > > _THIS_IP_ will not be sufficient in this case as it will print only > the MMIO accessors itself which is of not much use since it is not > inlined as below for example: > > rwmmio_read: readl+0x4/0x80 width=32 addr=0xffff8000087447f4 > rwmmio_post_read: readl+0x48/0x80 width=32 val=0x4 addr=0xffff8000087447f4 > > So in order to handle this second case as well irrespective of the compiler > optimizations, add _RET_IP_ to MMIO trace to make it provide more accurate > debug information in all these scenarios. > > Before: > > rwmmio_read: readl+0x4/0x80 width=32 addr=0xffff8000087447f4 > rwmmio_post_read: readl+0x48/0x80 width=32 val=0x4 addr=0xffff8000087447f4 > > After: > > rwmmio_read: qcom_smmu_tlb_sync+0xe0/0x1b0 -> readl+0x4/0x80 width=32 addr=0xffff8000087447f4 > rwmmio_post_read: qcom_smmu_tlb_sync+0xe0/0x1b0 -> readl+0x4/0x80 width=32 val=0x0 addr=0xffff8000087447f4 > > Fixes: 210031971cdd ("asm-generic/io: Add logging support for MMIO accessors") > Signed-off-by: Sai Prakash Ranjan Acked-by: Steven Rostedt (Google) What tree should this go through? -- Steve